In this section: |
Your migrated application will have dependencies on the existence and location of particular directories, files, permissions, and environment variables on the target system. This section explains how to configure the target environment in preparation for using iWay Service Manager with your applications.
The target environment configuration tasks are performed outside of the iWay server environment using native operating system tools rather than the iWay Service Manager GUI tools, such as, the Web console, iWay Designer, and iWay Integration Tools. The tool you use depends on your system and preference. Typically, on Windows platforms you will use a graphical user interface (GUI), while on UNIX platforms you will use a command line interface.
Important: Before beginning the configuration, be sure that iWay Service Manager on the target server is not running.
iWay functions that make use of system directories are:
To begin, set up a directory structure on the target system that mirrors the source iWay environment, and verify that these directories have appropriate permissions. If your application makes use of iWay special registers for directories, you can be flexible with new directory assignments during the migration. In this case, be sure to set up the new directories as needed and set the iWay Service Manager special registers appropriately.
Many protocols and extensions require the presence of third-party support jar files to function. It is helpful to catalog those that are required by your application. This can include files for:
Copy or acquire appropriate versions of the support files and add them to the target environment.
Your application may have required patches, PTFs, and so on, for the operating system or third-party products. See the appropriate vendor documentation for information on these items.
Download Sun Java version 1.5 or version 1.6 from http://java.sun.com/products/archive/ and install it according to vendor instructions. After installation, confirm that the PATH environment variable on the target machine is set correctly with the location of the Java executable.
Note:
Set the LIBPATH environment variable for protocols that require non-Java 3gl library support. Be aware that the name of the LIBPATH environment variable may be system dependent, for instance, other common conventions are LD_LIBRARY_PATH and SHLIB_PATH.
Should any be required, set the JVM options through the _JAVA_OPTIONS environment variable, where you can specify memory allocation and other performance enhancing features. On Windows only, JVM options can be added through the iWay Service Manager Web console under the Server, Settings, Java Settings, Startup Options section.
Add the required environment variables to the user profile for the iWay account so that the values are set automatically.
For more information on setting LIBPATH for iWay supported protocols, see the iWay Service Manager Protocols Guide.
| iWay Software |