Registering EPM System Web Server as a Partner Application

  To register EPM System web server as a partner application:

1. Open a console on the server that hosts the Oracle HTTP Server that front-ends the OSSO Server and navigate to ORACLE_HOME/sso/bin directory of Oracle HTTP Server, for example to C:/OraHome_1/sso/bin (Windows).

2. Execute a command similar to the following with -remote_midtier option:

   ssoreg.bat -site_name epm.myCompany.com 
   -mod_osso_url http://epm.myCompany.com:19400 
   -config_mod_osso TRUE
   -update_mode CREATE 
   -remote_midtier 
   -config_file C:\OraHome_1\myFiles\osso.conf
   

   The following explans the parameters used in this command. In this description, partner application refers to the Oracle HTTP Server that is used as the EPM System web server.

   • -site_name identifies the web site of the partner application; for example, epm.myCompany.com.

   • -mod_osso_url indicates the partner application URL, in PROTOCOL://HOST_NAME:PORT format. This is the URL at which the EPM System web server accepts incoming client requests, for example, http://epm.myCompany.com:19000.

   • -config_mod_osso identifies that the partner application uses mod_osso. You must include the config_mod_osso parameter to generate osso.conf.

   • -update_mode indicates the update mode. Use CREATE, the default, to generate a new record.

   • -remote_midtier specifies that the mod_osso partner application is at a remote mid-tier. Use this option when the partner application is at a different ORACLE_HOME than that of the OSSO Server.

   • -virtualhost indicates that the partner application URL is a virtual host. Do not use this parameter if you are not using a virtual host.

     If you are registering a partner application URL tied to a virtual host, you must define the virtual host in httpd.conf. See Optional: Defining Virtual Host.

   • -config_file indicates the path where osso.conf file is to be generated.