MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
226
Implementer Server must be able to communicate with MKS Integrity Server for the
integration to work successfully.
A common diagnostic technique when resolving MKS Integrity connectivity issues is to
ping the hostname (or IP address) of MKS Integrity Server. This technique is effective
provided you ping the server from the correct host.
When Implementer Server is installed on an iSeries, the iSeries must be able to
communicate with MKS Integrity Server.
When Implementer Server is installed on a PC, that PC must be able to
communicate with MKS Integrity Server. In this case, the iSeries is not actually
communicating with MKS Integrity Server, thus, it is meaningless if you can ping
MKS Integrity Server from the iSeries.
If you have Windows XP Service Pack 2 (SP2) installed on the system running
Implementer Server, the firewall built into SP2 could interfere with server
communications. You may need to adjust the firewall to allow connections on the Server
and Adapter ports, or disable it entirely.
For additional troubleshooting information, see the table on page 302.
Defining MKS Integrity Values in Implementer
The MKS Integrity communication parameters are defined in Implementer on the
MKS Integrity Setup panel.
Your Implementer user profile must have authority to maintain System Control (defined in
Work with Users) to change the default values on the MKS Integrity Setup panel. Without
this authority, changes are not allowed and the panel is protected.
To define MKS Integrity values in Implementer
1 From the Implementer Menu, type option 47, MKS Integrity, and press ENTER, or issue
the STRIM *INTMGRSET command.