Changing the Address of MCS

When you use Management & Control Services (MCS) to manage terminal IDs, you specify the DNS name or IP address of MCS when you install your requestor. If the MCS address changes after installation, you must change the address for the requestor.

To change the MCS address for a COM requestor
For the COM requestor, the IDManagerAddress field is a Value Name : Value String pair in the registry. It is located with regedt32.exe as follows:
Registry Key Values
\HKEY_LOCAL_MACHINE\SOFTWARE\Attachmate\Synapta\ServicesBuilder\3270\Bridge\IDManagerLocation
Value Name:     IDManagerAddress
Value String:   111.222.333.444

or

Value Name:     IDManagerAddress
Value String:   MyServer.MyCompany.com
To change the MCS address for a .NET requestor
For the .NET requestor, the IDManagerAddress field is a Value Name : Value String pair in the registry. It is located with regedt32.exe as follows:
Registry Key Values
\HKEY_LOCAL_MACHINE\ SOFTWARE\Attachmate\Synapta\ServicesBuilder\3270\Bridge\IDManagerLocationWS
Value Name:     IDManagerAddress
Value String:   111.222.333.444

or

Value Name:     IDManagerAddress
Value String:   MyServer.MyCompany.com
To change the MCS address for a Java requestor
To set the address of the MCS ID Manager for a java application, modify the BridgeAPI.properties changing the line ‘IDManager=’ using your favorite editor the Address of the ID Manager can be specified as a dotted IP address or the machine name as recognized by DNS in your environment.

The following 3 lines are a sample of the BridgeAPI.properties file specifying the MCS ID Manager address of “1.2.3.4”:

# Used in the BridgeAPI interface to designate
# the location of the idmanager server
IDManagerAddress=1.2.3.4

In order to modify the BridgeAPI.properties file use one of the following procedures:

  • In order to change the ID Manager location using winzip for a previously installed Java client:

    1. Locate and load into winzip the BridgeAPI.jar file referenced by your applications –classpath.

    2. Extract the BridgeAPI.properties file from within the BridgeAPI.jar to the c:\com\attachmate\cicsbridge\ws\BridgeAPI.properties file.

    3. Using a text editor change the IDManagerAddress= parameter to be either the dotted IP address or the server DNS name of the IDManager machine.

    4. Delete the BridgeAPI.properties from BridgeAPI.jar.

    5. Add the now modified c:\com\attachmate\cicsbridge\ws\BridgeAPI.properties into the BridgeAPI archive.

    6. Save the modified BridgeAPI.jar back to its location specified in the classpath for your application.

  • In order to change the ID Manager location using the jar utility for a previously installed Java client:

    1. Extract the BridgeAPI.properties file with

      jar -xvf com\attachmate\cicsbridge\ws\BridgeAPI.jar com/attachmate/cicsbridge/ws/BridgeAPI.properties.

    2. Using a text editor such as notepad, edit the newly extracted BridgeAPI.properties file.

    3. Replace the BridgeAPI.properties file with

      jar -uvf com/attachmate/cicsbridge/ws/BridgeAPI.jar com/attachmate/cicsbridge/ws/BridgeAPI.properties

      Note that in the above jar utility example all commands are issued from the root directory.

To change the MCS address for a J2EE RA or EJB requestor
  • In the BridgeAPI.properties file in the BridgeAPI-ra.jar (note: BridgeAPI-ra.jar is in the BridgeAPI.rar which is in the BridgeAPI.ear), update the IDManagerAddress field wiith the new IP address or DNS name of your MCS computer.

    See Packaging Enterprise Applications for more information.

Related Topics
Bullet Managing CICS Terminal IDs, Overview
Bullet Installation, Overview
  Footer