Table Of Contents
Installing PAP on Linux/Solaris
Installing PAP on Linux/Solaris
To install CEPM V126.96.36.199 PAP on a Linux machine, follow these steps:
Step 1 Complete Steps 1 through 18 in Chapter 3 "Common Installation Steps."
Step 2 Execute the database procedures in the following way:
Table 7-1 Executing DB Procedures
To execute the procedure in Oracle 9i, open any Oracle client (such as SQL Plus, Benthic, Putty etc.) and run the pap.sql and pdp.sql files from the /CEPM-V188.8.131.52/db/scripts/oracle/oracle9i folder.
Example: Open the Oracle Client `SQL Plus' and use the following command to invoke pap.sql in the client:
SQL> @ opt/CEPM-V184.108.40.206/db/scripts/oracle/oracle9i/pap.sql
Note If you are using Oracle 11g (Version 220.127.116.11 in particular), before executing the DB scripts, add the following parameter in Oracle 11g configuration files, that is, ora.init: deferred_segment_creation=false
To execute the procedure in Oracle 10g or 11g, open the Oracle client (use SQL Plus only) and run the pap_wrapped.sql and pdp_wrapped.sql files from the /CEPM-V18.104.22.168/db/scripts/oracle folder.
If you get any drop-type error while running these wrapped sqls, ignore the error and resume the installation process.
It is highly recommended to run the wrapped sqls at the client end. These sqls are masked code which cannot be read normally and can be understood only by Oracle. If you open any _wrapped sqls, you do not find anything in a readable format. These wrapped sqls are supported from Oracle10g onwards. However, if you use Oracle9i, you can run the regular sqls.
To execute the procedure in MS SQL Server, open the MS SQL client and run the pap.sql and pdp.sql file from /CEPM-V22.214.171.124/db/scripts/mssql folder. For MSSQL 2000, these scripts are available in /CEPM-V126.96.36.199/db/scripts/mssql/mssql2000 folder.
It is recommended to run these scripts in MSSQL Query Analyzer, because executing these scripts through SQLCMD might not compile all the functions and procedures.
Note If you are not using a shared repository, run dbutility.sql to enable JMS DB sync. Before running these files, you must update the pap_config.xml and pdp_config files to give effect to the PAP PDP database separation. Refer to Chapter 11 "JMS Configuration for PAP-PDP Database Separation" to know how the <jms> tags of these files are updated.
Step 3 Deploy the PAP WAR files by starting the application server using one of the following methods:
If you are using a prepackaged Tomcat application server, WAR files are deployed during above installation steps. WAR files are copied in .../CEPM-V188.8.131.52/external/apache-tomcat-5.5.17/webapps directory. Thus, no separate deployment is required. You can directly start the CEPM using the startcepmgui.sh file from the .../CEPM-V184.108.40.206/bin folder.
Note CEPM is set by default to use the identical ports (8080 and 8005). This may cause conflict when any other process uses these ports. To change the port numbers for Cisco, modify the Server SHUTDOWN port number and the CONNECTOR port number in the server.xml file located at CEPM-V220.127.116.11/external/apache-tomcat-5.5.17/conf folder.
Note You can also enable an SSL HTTP/1.1 Connector on port 8443 in the server.xml file. Refer to Chapter 18 "SSL Configuration" to know how to configure SSL in CEPM.
–Edit the Tomcat_home/bin/catalina.sh file by appending the JAVA_OPTS variable with -DCEPM_HOME=<folder path of CEPM-V18.104.22.168>
–Copy the cepm.war file from the dist folder to the application folder and deploy these files.
–Start the server.
If you are using the BEA WebLogic Server:
–Edit the startWebLogic.cmd file from $BEA_HOME/User_Projects/Domains/<Domain Name>/bin folder by adding the following parameter after %JAVA_OPTIONS% (after every occurrence) under @REM START WEBLOGIC section
For example, -DCEPM_HOME=/CEPM-V22.214.171.124
–Open config.xml file from $BEA_HOME/user_projects/domains/DOMAIN_NAME/config folder and add the following tag under <security-configuration> tag:
–Copy the cepm.war file from .../CEPM-V126.96.36.199/dist folder to $BEA_HOME/User_Projects/Domains/<Domain Name>/Application folder.
–Open the WebLogic console in your web browser and deploy the cepm.war file. (Refer to "Deployment of .war File in WebLogic 9.2/10" section.)
–Start the server.
If you are using WebSphere, start the server by running the ../WebSphere/AppServer/bin/startServer.sh file and follow these deployment instructions:
–Login to Websphere administrative console.
–Choose Servers > Application Servers.
–Click the name of the server link. Ex: Server1
–On the Configuration tab, in the Server Infrastructure section, select Java and Process Management and Process Definition.
–On the Process Definition page, select Java Virtual Machine from Additional Properties.
–In the Java Virtual Machine, select Custom Properties from Additional Properties
–In the Customer Properties, click New.
–In the Configuration tab, specify the name, value, and description.
Ex: Name: CEPM_HOME
Description: Not mandatory
–Restart the WebSphere server
–Deploy cepm.war file. (Refer to "" section.)
This process installs PAP and PDP on your system. After completing this step, you can access the administration console application through a web browser.
If the server throws any exception at this stage, see Chapter 15 "Troubleshooting CEPM Installation."
Step 4 Licensing Info: As per the licensing agreement you are subjected to use the application with a limited validity period. Refer to Chapter 14 "Updating CEPM License" if the validity period is lapsed.
Step 5 Verify whether the PAP and PDP are installed successfully. See Chapter 13 "Verifying PAP-PDP Installation."
For further information on using the administration console, see the Cisco Enterprise Policy Manager Quick Start Guide or the Cisco Enterprise Policy Manager User Guide.