Product guide

3 Select the General tab.
4 Under Service status, click Stop. The server is now stopped.
5 Copy the required files for your ticketing server, then repeat steps 1-3.
6 Under Service status, click Start. The server is now running.
Copying the Remedy files
Use this task to copy the files required for the Remedy extension. For information about these
files, see your Remedy documentation. The Remedy extension includes support for the Remedy
6.3 and 7.0 servers.
NOTE: You can use the Remedy 5.1 or 7.0 API files for the Remedy extension. McAfee does
not support an integration with the Remedy 5.1 server, but the 5.1 API files will work for
integrations with the Remedy 6.3 or 7.0 servers. However, the Remedy 6.3 API files are not
supported.
Before you begin
• Stop the server.
• If using the Remedy 5.1 API files, locate these required files to copy:
• arapi51.dll
• arjni51.dll
• arrpc51.dll
• arutl51.dll
• arapi51.jar
• arutil51.jar
• If using the Remedy 7.0 API files, locate these required files to copy:
• arapi70.dll
• arjni70.dll
• arrpc70.dll
• arutiljni70.dll
• arutl70.dll
• arxmlutil70.dll
• icudt32.dll
• icuin32.dll
• icuuc32.dll
• arapi70.jar
• arutil70.jar
Task
1 Copy these required files to the \Server\bin folder of your Policy Auditor installation. For
example, C:\Program Files\McAfee\ePolicy Orchestrator\Server\bin.
• If using the Remedy 5.1 API files:
• arapi51.dll
• arjni51.dll
Managing Issues and Tickets
Working with ticketing servers
65McAfee Policy Auditor 5.0 Product Guide