Configuring CA XCOM Data Transport Trusted Security with IBM DB2

Document ID : KB000019798
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This document will guide you in configuring XCOM's Trusted security using IBM DB2.

Solution:

Starting with XCOM r11.5 for Windows Family, configuring the Trusted Security will require that IBM's DB2 or MySQL be installed on a server. Here are the steps to follow in order to configure your CA XCOM Trusted security with IBM DB2.

  1. Make sure that you have IBM DB2 UDB v9 or later installed on a server.

  2. Create the XCOMTRST database in DB2. You can change the name of the database, but for these steps we will keep it as XCOMTRST since the sample .sql member to create the tables make use of the XCOMTRST name.

  3. Create the necessary tables in the XCOMTRST database. We provide the user with a member called "xcomtrstDB.sql" in our XCOM_HOME\config directory.

  4. Make a copy and modify the "xcomtrstDB.sql" file to be used with DB2. That would require that you remove some lines from the file that are related to MySQL.

  5. Using IBM's DB2 Command Editor you can open the "xcomtrstDB.sql" file you already modified and run it. You should see the results on the Command Editor window.

  6. Once you have created the XCOMTRST database with its tables you can now configure the ODBC and JDBC connection.

  7. Configuration of ODBC:

    Note: XCOM is a 32 bit application and that would require that you setup a 32 bit ODBC connection.

    1. If you installed or are running IBM DB2 32 bit then configuring the ODBC should be straight forward:

      • go to Control Panel, System & Security, Administrative Tools, and finally to Data Sources (ODBC)

      • you will notice that there are 3 tabs for setting DSN. You will need to set the User and System DSN tabs.

      • in each tab you will click the Add button and scroll down until you find the DB2 ODBC driver, highlight it and click Finish

      • fill in the form with the necessary information such as Data Source Name, Database, and Data Alias

    2. If you installed or are running IBM DB2 64 bit then you will need to do the following to setup a 32 bit ODBC for XCOM:

      • you will need to run the 32 bit ODBC version, odbcad32.exe, which is located in your c:\Windows\SysWOW64 directory

      • you will then configure the User and System DSN tabs as mentioned above.

  8. A JDBC driver is required for the Trusted database. To install it you would need to copy the "db2jcc" and "db2jcc_license_cu" jar files into our XCOM_HOME\lib directory or place the path in the CLASSPATH Environmental Variable.

  9. Now we are ready to configure the necessary CA XCOM parameters to make sure that a connection to the database is successful in order to continue with the configuration of the Trusted database.

  10. Start the XCOM GUI and click on the Global Parameters tab.

  11. You will find a section called Trusted, expand the section and fill in the parameters with the proper values.

  12. Click on the Test button once you have filled in all of the parameters and you should get a pop-up window with messages indicating if XCOM has connected successfully or not to the database. If successful you can continue with configuring the Trusted Transfer tab. Otherwise, debug any of the messages received with your DB2 administrator or contact us.

  13. Save all the changes and stop/start the xcomd service.

Configuring the Trusted Transfer tab:

  1. Start the XCOM GUI

  2. Click on the Trusted Transfer tab and on the Remote System link on the left side of the screen. This will allow you to define the remote system from where the trusted transfer will be sent from.

    You can add the remote system by specifying the SYSID and SYSNAME values or by specifying the IP address of that remote system in the Remote System field. Click on the Add button.

  3. You can then click on the Manage Users link on the left side of the screen. This will allow you to define the valid userid for the Trusted transfer. Please keep in mind that the userid must match on both systems and must exist on the Windows side. If sending from the mainframe, chances are that the userid of the person submitting the job is in upper case. Make sure to define the userid in upper case in this panel. Otherwise, the transfer will fail.