Before starting InterChange Server

Before you start InterChange Server, verify that the supporting software is running and that the configuration file is set up correctly. The following topics explain how to do this:

Verifying and adding environment variables

To ensure that your system recognizes commands that are generated by the InterChange Server system, you must check the system variables. The CWSharedEnv.bat file includes the environment variables that InterChange Server needs. If any system variables are missing, you must add them.

Verifying environment variables

  1. Open a Command Prompt window:

    Click Start > Programs > Accessories > Command Prompt

  2. Type set in the command prompt window, then press the Enter key.

    All of your system variables appear in alphabetical order.

    Tip:
    To make the text in the Command Prompt window easier to read, right-click the title bar, then select Properties. In the Layout tab, increase the height and width of the Window Size. In the Colors tab, select a different color for the Screen Text. Click OK, select "Modify shortcut which started this window," then click OK again. The next time you open this Command Prompt window, the new properties take effect.
  3. Make the classpath, CROSSWORLDS, and Path system variables include the WebSphereICS and WebSphere MQ values listed in Table 13.

    If you do not see one of the variables, you may need to scroll up or resize the window. Follow the instructions in the Tip that precedes this step.

    The values listed in Table 13 are examples of InterChange Server variables in the CWSharedEnv.bat file if you installed the InterChange Server software and supporting software on the C:\ drive. These examples do not include the database variables, so you may also see DB2, Oracle, or MS SQL values in addition to these InterChange Server values.

    If any of the system variables listed in Table 13 are missing, proceed to Verifying and adding environment variables. If all system variables are listed, proceed to "Before starting InterChange Server".


Table 13. Classpath, CROSSWORLDS, and Path system variables

Variable Value
CLASSPATH C:\IBM\WebSphereICS\lib\rt.jar;<DB2Home>\java\db2java.zip
CROSSWORLDS
C:\IBM\WebSphereICS
CWTools.home422
C:\IBM\WebSphereICS\bin
MQ_LIB
C:\Program Files\IBM\WebSphere MQ\java\lib
Path C:\IBM\WebSphereICS\bin;C:\IBM\WebSphereICS\jre\
bin\;C:\IBM\WebSphereICS\jre\bin\classic;
C:\Program Files\IBM\WebSphere MQ\
tools\c\samples\bin;
C:\Program Files\IBM\WebSphere MQ\bin;
C:\Program Files\IBM\WebSphere MQ\Java\lib

Adding environment variables

If any of the InterChange Server system variables listed in Table 13 are missing from your system variables, you must add them. To add System variables, follow these steps:

  1. Click Start > Settings > Control Panel, then double-click System.
  2. In the Advanced Tab, click the Environment Variables button.
  3. Click the New button below the list of system variables.
  4. In the New System Variable dialog box, type the variable name in the Variable field and the value in the Value field, then click OK.
  5. Repeat steps 3 and 4 for each new variable.
  6. Reboot the machine to set the new system variables.

Verifying that supporting software is running

To verify that supporting software is running, you must take the following steps:

Starting the Persistent Naming Server

The IBM Transient Naming Server (tnameserv) is the part of the IBM Java ORB that provides the naming service for the WebSphere business integration system. When a component starts, it registers itself with the IBM Transient Naming Server. When the component needs access to another business-integration-system component, it uses the naming service to determine the information it needs to locate and start interacting with that component. For example, when an adapter must communicate with InterChange Server, it obtains the location of InterChange Server through the Transient Naming Server.

However, if the Transient Naming Server fails, its memory contents are lost. As a result, all components that had been registered with it must be rebooted to reregister with the naming service. The Persistent Naming Server extends the capability of the IBM ORB Transient Naming Server so that the collection of persistent CORBA objects that are registered with the Transient Naming Server are stored in a naming repository, which makes them available to other processes and ICS components in the event that the Transient Naming Server fails. Other components do not need to shut down and restart to reregister with the naming service.

By default, the Persistent Naming Server is enabled; that is, references to CORBA objects are maintained in the naming repository. However, for this naming server to run, you must explicitly start it with the PersistentNameServer.bat startup file, located in the bin subdirectory of the product directory. This startup file performs these tasks:

  1. Start the IBM ORB Transient Naming Server.
  2. Start the Persistent Naming Server to load the referenced CORBA objects into the naming repository.

Note:
You can also start the IBM Transient Naming Server and the Persistent Naming Server as a Windows service. For more information, see Running components as Windows services.

For more information about how to start the Transient Naming Server and Persistent Naming Server, see the information on how to configure the ORB in the System Administration Guide.

HA

For the high availability environment, the Persistent Naming service must be started as a Windows Service.

Verifying services for ICS components

The WebSphere InterChange Server Installer automatically installs InterChange Server as a Windows service. You can also install the following ICS components as Windows services:

To install one of these components as a Windows service, use the CWServices utility. For more information on this tool, see Running components as Windows services.

To verify that Windows services have been created and started for ICS components, follow these steps:

  1. Click Start > Settings > Control Panel, then double-click Administrative Tools.
  2. Double-click Services.
  3. Scroll to the following services and make sure each is started (for whichever database is being used):

    Table 14. Database server and Windows services

    Database server Windows service
    DB2 DB2-DB2
    Oracle Oracleservicecwld Oracle database instance
    SQL Server MSSQLServer
  4. If any of the services are stopped, right-click the service, then select Start.
  5. If any of these services are configured to start manually, right-click the service, select Properties, then select Automatic from the Startup Type list.

Verifying the configuration file

Installer creates the InterchangeSystem.cfg file using values that you enter in the installation screens. Before you start InterChange Server, make sure that the values in this file are consistent with the values you used in setting up your database.

From the Server Instances console tree of System Manager, right-click your InterChange Server name and select Edit Configuration.

Copyright IBM Corp. 1997, 2004