02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 5: <strong>MKS</strong> Integrity Integration<br />

<strong>MKS</strong> Source/<strong>MKS</strong> Integrity<br />

Integration Properties<br />

Troubleshooting<br />

302<br />

<strong>MKS</strong> Source/<strong>MKS</strong> Integrity Integration Properties<br />

Description<br />

DefaultIMEnvironment Default <strong>Implementer</strong> *TST environment on the iSeries to check out to in the<br />

Export to <strong>Implementer</strong> function. This is an optional property.<br />

DefaultProject Default <strong>Implementer</strong> project to use in the Export to <strong>Implementer</strong> function.<br />

DefaultStagingLocation Default IFS location on the iSeries where to pull objects from.<br />

For each slash in the actual name, define the property with two slashes (//).<br />

For example, if the default IFS location is /home/mydirectory, specify<br />

//home//mydirectory. This is an optional property.<br />

The following information can help you resolve common problems with <strong>Implementer</strong> Server.<br />

Symptom Possible Cause Resolution<br />

Using ICTLSVR<br />

*START, F7=Test in<br />

<strong>MKS</strong> Integrity Setup<br />

panel, or F7=Test in<br />

<strong>MKS</strong> Source Setup<br />

panel results in error<br />

VIM8598 “Unable<br />

to communicate<br />

with the <strong>MKS</strong><br />

Integrity<br />

Server”.<br />

#1: IP address for system running <strong>Implementer</strong><br />

Server is not in <strong>MKS</strong> Integrity config file<br />

IntegrityClientSite.rc.<br />

Also see <strong>MKS</strong> Integrity weblogic.log for error<br />

message with missing IP, for example:<br />

Thu Feb 9 14:32:25 CDT <strong>2006</strong>:<br />

<br />

* * * * ERROR * * * * (0):<br />

ICAllowSpecificConnectionPolicy failed<br />

the connection. Connection: 10.17.4.6:<br />

is not on the list of acceptable<br />

machines.<br />

#2: Network may not be configured to communicate<br />

between the system running <strong>Implementer</strong> server<br />

and system running <strong>MKS</strong> Integrity.<br />

From system running <strong>Implementer</strong> Server, ping<br />

system where <strong>MKS</strong> Integrity Server is located (see<br />

<strong>MKS</strong> Integrity Setup panel, Server port field).<br />

<strong>Implementer</strong> Server running on iSeries, from<br />

command line issue<br />

ping <br />

(IP address must be in single quotes .<br />

<strong>Implementer</strong> server running on a PC, from<br />

command prompt run ping .<br />

In the IntegrityClientSite.rc<br />

file, specify the IP addresses for the<br />

system running <strong>Implementer</strong> Server<br />

and the localhost (127.0.0.1) in<br />

daemon.validConnectionList=<br />

For details, see “Modifying the<br />

<strong>MKS</strong> Integrity Server Configuration<br />

File” on page 206.<br />

Verify and correct network<br />

configuration.<br />

Specify correct system running<br />

<strong>MKS</strong> Integrity Server in Server port<br />

field on <strong>Implementer</strong>’s <strong>MKS</strong> Integrity<br />

Setup panel and/or <strong>MKS</strong> Source<br />

Setup panel. For details, see<br />

“Defining <strong>MKS</strong> Integrity Values in<br />

<strong>Implementer</strong>” on page 226, and<br />

“Defining <strong>MKS</strong> Source Values in<br />

<strong>Implementer</strong>” on page 275.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!