setup.exe, from the root of the CD in the clientinst directory, which also runs the Client Support opiton.If you are building a server-based application to run on the same server where the run-time service is installed, after setting your class path, no additional configuration is necessary.
However, if you plan to run your applications on a computer other than the computer on which the run-time is installed, you need to provide the necessary client support files for your environment on all of the computers you will use. The Client Support option, available from the installation program, installs the tools (the IMSClient and all its support JARs) your application needs to run its host access tasks.
|
Alternatively, you could use setup.exe, from the root of the CD in the clientinst directory, which also runs the Client Support opiton. |
When you install Services Builder for IMS on a Windows platform, along with other component install options, you can select to install the client support JARs and properties files required for Java clients and the COM interface required for NativeWin32 clients. You are also prompted to install IMS Connector Proxy Service, a Windows service that is required for .NET Web services and other stateless Win32 clients.
When you install Services Builder for IMS in a UNIX environment, you will have the same option to install the necessary client support files.
Once the client installation is finished, a IMSClient directory is created under install_directory\Attachmate\EAI\, and in this directory will be the IMSConnectorProxyService.exe, IMSConnector.dll, and JARS required for the client to run IMS tasks.
In addition to installing the appropriate client support files, you need to make sure that the following files, which are installed by the Client Support option, are in your class path on the computer where you will compile your applications, and from where they will be served.
install_directory/Attachmate/EAI/IMSClient, where, by default, the install directory is c:\program files:
| IMSClient.jar
xerces.jar common.jar MetaData.jar Util.jar ra-client.jar clientconfig.jar |
..\EAI\Common\mcs:
| mcsagent.jar
mcs-rpc.jar |
EAI\Common\config directory, which includes the ims_client.properties file.
By later editing this file, you can enable client-side logging and tracing.
|
In some instances, it may not be advantageous to add ims_client.properties to the class path of the client computer (for example, applications that run on some application servers). However, as the ims_client.properties file is also placed in the directory specified by the system property, <user.home>\cfg, this does not present a problem.
This is a platform-specific directory where Java puts per-user data. You can determine the value of |
install_directory/Attachmate/EAI/IMSClient:
| xml-apis.jar
xalan.jar |
 |
|
 |
Configuring the Runtime Service |
|
Associating Tasks with Run-time Servers |
|
Starting and Stopping the Runtime Service |
 |
Manually Configuring the Client Environment |
 |