Setting up the integration

To set up the integration, you must ensure that the Developer for z/OS® Eclipse workspace uses the correct file encoding, connect to a z/OS system, and enable the Developer for z/OS client to access a Git repository.

Setting up workspace file encoding

Rocket Git requires that files stored in the z/OS repository be encoded in UTF-8. Because the default file encoding for Eclipse workspaces created on the Windows operating system is Cp1252, any workspaces that are not explicitly encoded with the git-encoding=utf8 tag default to the operating system setting. The default workspace encoding can cause file transfer issues when you try to store the files in Rocket Git.IBM® Developer for z/OS Eclipse workspaces that you use for the Dependency Based Build (DBB) integration must use UTF-8 file encoding and Unix file line delimiters. To ensure that files in the Eclipse workspace meet these requirements:
  1. In the Preferences window, expand General and click Workspace.
  2. In the Text file encoding area, click Other and select UTF-8 from the list.
  3. In the New text file line delimiter area, click Other and select Unix.
  4. Click Apply and Close.
  5. Restart IBM Developer for z/OS.

Connecting to a remote system

Connect to the remote system where DBB is installed and the source files are to be built. For more information about connecting to a remote system see these topics or watch the demonstration.
How to connect to a remote system

Enabling access to GitHub

If you want to use GitHub repositories, such as the DBB sample repository, with Developer for z/OS you must generate a security certificate for the client and add it to your GitHub account.

  1. Generate security certificates for the Developer for z/OS client:
    1. On the Preferences window, navigate to General > Network Connections > SSH2.
    2. On the General tab, verify the location for storing generated keys. If the location is not correct, click Browse to change the location for generated keys.
    3. On the Key Management tab, click Generate RSA Key.
    4. In the Passphrase and Confirm passphrase fields, type a password or passphrase for the RSA key.
    5. Click Save Private Key. The client generates two RSA key files: id_rsa and id_rsa.pub.
    6. Open id_rsa.pub and copy the contents to the clipboard. You will use these contents in step 2.
  2. Add the generated SSH key to your user profile on the GitHub server.
    1. Open the GitHub server where your code repository is.
    2. On the GitHub toolbar, click your profile and select Settings. The Account settings page opens.
    3. Select SSH and GPG keys, and then click New SSH key. The new SSH key wizard opens.
    4. In the Title field, type a name, such as IDz client.
    5. In the Key field, paste the copied content of ~/.ssh/id_rsa.pub.
    6. Click Add SSH key.

What to do next