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.

<strong>Implementer</strong> Server Patches and PTFs<br />

<strong>Implementer</strong> and <strong>MKS</strong> Integrity Integration<br />

<strong>Implementer</strong> provides patches for <strong>Implementer</strong> Server in the standard <strong>Implementer</strong> PTF<br />

format. When a patch for <strong>Implementer</strong> Server is included with a PTF, the PTF installer<br />

automatically installs the patch into the server directory.<br />

The patches usually distribute as CLASS files (as opposed to JAR files) to allow applying<br />

incremental patches. The class files install into the IFS location:<br />

/mks/implementer//webapps/ROOT/WEB-INF/classes<br />

IMPORTANT If <strong>Implementer</strong> Server runs on a PC, after applying a patch you need to<br />

recopy the server from the IFS to the system where the server runs. Follow the same<br />

instructions as when initially installing the server. You do not need to reinstall the<br />

service.<br />

When you apply an <strong>Implementer</strong> Server patch, a marker file is created in the ‘info’<br />

subdirectory. The marker file identifies which issue the patch applies to. If you apply<br />

multiple patches, then multiple marker files are created in the subdirectory. The marker file is<br />

in the form IMPTFnnnn, where nnnn is the issue number associated with the PTF.<br />

Troubleshooting <strong>Implementer</strong> Server<br />

If you encounter errors with <strong>Implementer</strong> Server, the <strong>Implementer</strong> Server log files register<br />

server activity based on the logging level you define in <strong>Implementer</strong> Menu option 49,<br />

<strong>Implementer</strong> Server.<br />

Server activity for the current date is stored in file implementer-server.log. When the<br />

current date changes, implementer-server.log renames to a date differentiated file name,<br />

and an empty implementer-server.log file is created. The server log files are purged<br />

based on the number of days you specify to retain on the <strong>Implementer</strong> Server Setup panel.<br />

When <strong>Implementer</strong> Server runs on the iSeries, the server log files are stored in the<br />

/logs sub-directory of the IFS. The <strong>Implementer</strong> Display Server Log (IDSPSVRLOG)<br />

command allows you to view history logs. The command has one parameter, DATE,<br />

which accepts the value *CURRENT, or a specific date you enter in YYYYMMDD<br />

format.<br />

IMPORTANT Your user profile must have authority to System Control Maintenance to<br />

issue the IDSPSVRLOG command.<br />

When <strong>Implementer</strong> Server runs on a PC, the log files are stored in the /logs subdirectory<br />

on the PC. You can view the history logs using any standard text editor, such<br />

as Notepad.<br />

225

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

Saved successfully!

Ooh no, something went wrong!