In this section: |
After installation, review the following topics and perform the steps needed for your environment.
After installation, an iway7 directory is created and contains the following subdirectories:
Contains files required to start and access iWay Service Manager.
Contains configuration files for iWay components. Schemas and some web services information are written to subdirectories.
User IDs used to run iWay components must have full permissions to the config directory.
Note: You can run more than one instance of Service Manager by defining multiple configurations using the iWay Service Manager Administration Console. The iWay Service Manager Administration Console is introduced in Configuring iWay Components. By default, two configurations are defined, base and raw. The base configuration sets up everything you require to get started and includes SOAP and HTTP listeners. The raw configuration contains no listeners and provides a useful template to define additional configurations.
Contains documentation, miscellaneous tools, and files to configure additional components. Subdirectories of etc also contain Extensions and additional tools.
Contains adapters, drivers, and other files used by iWay components. All iWay components must access this directory and your library path must be set to this location. For details, see Environment Variables.
Many protocols that iWay Service Manager supports require the presence of third-party jar files. Specific requirements are documented for each protocol in the iWay Service Manager Protocol Guide.
The j2ee.jar file is required for a number of iWay Service Manager features and functions across protocols.
J2EE is not a component that is normally distributed with JRE. If you are compiling an iSM exit that requires J2EE, Oracle provides a skeleton version that does not contain any method code. This version can be downloaded using the following link:
http://download.java.net/maven/2/javax/javaee-api/6.0/javaee-api-6.0.jar
The actual .jar file that contains the appropriate method code is licensed and supplied by the vendor of an application server (for example, Glassfish, JBOSS, and so on). The Apache Tomcat web server does not provide a J2EE, so you must locate the appropriate executable code. For example, you may need the mail.jar file from Oracle if you are using iSM mail systems.
There is a j2ee.jar file that is distributed by Oracle, which can be used. This file can be downloaded using the following link:
http://www.oracle.com/technetwork/java/javaee/download-141771.html
Download and install the software according to the instructions from the vendor and copy the j2ee.jar to [IWAYHOME]/lib.
For more information about your specific platform, contact iWay Customer Support.
Ebix archives are not packaged with the iWay 7.0.7 Service Manager installation. However, Ebix metadata is available for download from the following website, which is hosted and maintained by iWay Software and Information Builders:
http://techsupport.ibi.com
iWay Service Manager uses two TCP ports for system communication. The following table lists the function and default values of these ports.
Listener |
Default Port |
Purpose |
---|---|---|
Console |
9999 |
HTTP listener for the iWay Service Manager Administration Console. |
SOAP |
9000 |
SOAP listener for iBSP. |
During iWay SM installation, you can select values other than the default for either or both of these ports (for security or in case of a port conflict).
Under certain circumstances, it may be necessary to change the iWay Service Manager system port assignments after installation is completed. This section describes the procedures to change the Console and SOAP and iBSP port assignments.
The iWay Service Manager Administration Console port assignment can be modified by accessing the console and navigating to Console Settings.
The SOAP listener port is set to the integer value literal entered during iWay Service Manager installation, with the default being 9000. This is not ideal for situations where the SOAP port will be changed after installation, since the ibse-port Special Register and the SOAP port must always be changed in tandem.
The Listeners pane opens.
The Select listener type pane opens.
The value you are replacing should be an integer port number, its value being 9000 if the default was accepted during installation. Do not change any of the other properties of the SOAP1 listener.
Note: You only need to add the ibse-port Special Register in the SOAP1 Listener Port field once. After this has been set up, future changes to the ibse-port Special Register will automatically update the iWay Service Manager SOAP port.
Once you have successfully completed setting up the SOAP listener value to follow that of the ibse-port Special Register, changing the ibse-port register will automatically change the iWay Service Manager SOAP listener port, as well.
The console refreshes with the General Properties of the selected server.
A list of special registers appears in the right pane.
Note: This value must be an integer, within the range of valid port numbers, and currently not used by any other process on the machine. If necessary, contact your system administrator for assistance in choosing an available TCP port.
The Register Settings page is displayed so you can confirm the new ibse-port value.
As with all iWay Service Manager Special Register settings, you must restart the server for the new ibse-port setting to take effect.
The following message appears in your browser:
Server's master configuration is restarting...
When restart is complete, the iWay Service Manager Administration Console home page appears.
After installation, environment variables are required to use iWay adapters and components. The variables can be set in your profile.
Note: If you plan to run multiple installations of iWay components, the environment variables must be set up appropriately for each installation.
The following environment variable settings are required to use iWay Service Manager and iWay adapters and components on a UNIX system:
IWAY7
For example:
IWAY7=/home/userID/iWay7/ export IWAY7
Note: Be sure to include the trailing slash.
PATH=$PATH:/home/userID/iWay7/lib export PATH
Platform |
Variable |
---|---|
AIX |
LIBPATH |
HP-UX |
SHLIB_PATH |
Other UNIX Platforms |
LD_LIBRARY_PATH |
For example:
LD_LIBRARY_PATH=/home/userID/iWay7/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH
By default, the iwsrv executable program installs the iSM Windows service to run out of process.
For more information on the iwsrv executable program, see the iWay Service Managers User’s Guide.
If you wish to remove iWay from your system, do the following:
C:\Program Files\iWay7\config
iWay 7.0 Service Manager
You can also delete any iWay installation files in subdirectories of the following:
C:\WINNT\Downloaded Installations\ C:\WINDOWS\Downloaded Installations\
If you ran the deploy tool to configure components for an application server, run its uninstall utility as well, for example:
C:\Program Files\iWay7\etc\uninstall\deploy\uninstaller.exe
iWay Software |