Manually Deploying Web Applications

To manually deploy EPM System Web applications:

Install EPM System products using EPM System Installer.
Typically, EPM System Installer installs WebLogic Server for you. If you have an existing WebLogic Server installation and want to use it instead of the WebLogic Server installed by EPM System Installer, during installation, you must install EPM System products to the same Middleware home. If EPM System Installer detects an existing WebLogic Server installation in the installation location, it does not install WebLogic Server.
Note the requirements for installing Web applications in a distributed environment. See Installing EPM System Products in a Distributed Environment.
Launch EPM System Configurator using the following command and perform all required configuration tasks except for the “Configure Web Server” task. Note that the “Deploy to Application Server” task is not available.
Windows:
```
EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.bat
```
UNIX:
```
EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.sh
```
Launching EPM System Configurator with this command hides the Web application deployment tasks and skips the product registration with Shared Services task.
See Configuring EPM System Products.
Launch the Fusion Middleware Configuration Wizard: From the command line, change the directory to MIDDLEWARE_HOME/oracle_common/common/bin and launch config.cmd (Windows) or config.sh (UNIX).

Select Create a New WebLogic Domain and then click Next.

Note:

All EPM System products must be deployed to the same domain. If you have already deployed EPM System products, select “Extend an Existing WebLogic Domain.” Additionally, if you are using Financial Close Management, EPM System and Oracle SOA Suite must be deployed to the same domain. If you have already configured Oracle SOA Suite, deploy EPM System products to the same domain by selecting “Extend an Existing WebLogic Domain.”

A list displays all the Web applications installed in the Middleware home. For EPM System products, the list is generated from the configuration templates that were installed during installation with EPM System Installer.

Select Generate a domain configured automatically to support the following products, then select the EPM System Web applications you want to deploy, and then click Next.
Oracle recommends that you simultaneously configure all Web applications.
Enter the domain name and location and then click Next.
By default, the domain location is MIDDLEWARE_HOME/user_projects/domains.
Enter a user name and password for the domain administrator, and a domain description, and then click Next.
Select a WebLogic domain startup mode (Development or Production), specify which JDK to use, and then click Next.
You must select Production mode. Oracle recommends that you select the default JDK.
Configure the JDBC data sources, and then click Next.
For each Web application, specify the database connection information that you entered during database configuration with EPM System Configurator.
If you configured different databases for different products, enter database connection information separately for each Web application. Select the Web application, and then enter the connection information.
Tip:
EPMSystemRegistry is the Shared Services and Registry database.
The Configuration Wizard tests the database connection.
Review the Connection Result log, and then click Next.
For Managed Servers, Clusters and Machines, on the Configure Managed Servers panel, enter the listen ports and change them from the default value of 7001. See the Oracle Hyperion Enterprise Performance Management System Installation Start Here for a list of default ports.
Note:
If you change the ports from the defaults, you must also change them in the stop scripts located in MIDDLEWARE_HOME/user_projects/domains/EPMSYstem/bin.
For a distributed deployment, for Managed Servers, Clusters and Machines, on the Configure Machines panel, create a machine for each machine in the deployment.
For each managed server, assign the managed server to a machine.
(Optional) For Managed Servers, Clusters and Machines, on the Configure Clusters panel, you can set up a cluster. You can also set up a cluster after you've completed the deployment. For details on Web application server clustering, see (Optional) Clustering Web Applications in a Manual Deployment.
Review the Configuration Summary, and then click Create to create the domain and deploy the Web applications.
Web applications are deployed in offline mode.
For a distributed deployment:
1. Start the Node Manager on each machine in the deployment.
2. On the WebLogic Administration Server machine, pack the domain that you created.
3. Copy the pack to each machine in the deployment.
4. Unpack on each machine in the deployment.
WebLogic Server unpacks all Web applications on each machine in the deployment. On each machine, it runs the managed servers that you associated with the machine.
If you deployed Financial Close Management, perform additional manual steps. See Additional Postdeployment Steps for Financial Close Management.

Open MIDDLEWARE_HOME/user_projects/domains/domainName/config/fmwconfig/system-jazn-data.xml in a text editor, and after the last </grant> line in the file, add the following: (Note that these changes are also required if you deployed EPM System products to a domain hosted on another machine and the domain was not created with EPM System Configurator.)

<grant>
<grantee>
<codesource>
<url>file:${EPM_ORACLE_HOME}/products/Essbase/eas/server/lib/eascsf.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.service.credstore.CredentialAccessPermission</class>
<name>context=SYSTEM,mapName=CSF_EAS_MAP,keyName=*</name>
<actions>read,write,update,delete</actions>
</permission>
</permissions>
</grant>

<grant>
<grantee>
<codesource>
<url>file:${EPM_ORACLE_HOME}/common/CSS/11.1.2.0/lib/css.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class> 

<name>context=APPLICATION,name=*</name>
<actions>getApplicationPolicy</actions>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
<url>file:${EPM_ORACLE_HOME}/common/jlib/11.1.2.0/lib/registry-api.jar</url> 

</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.service.credstore.CredentialAccessPermission</class> 

<name>context=SYSTEM,mapName=epm_sys_reg_cred_map,keyName=*</name>
<actions>read,write,update,delete</actions>
</permission>
</permissions>
</grant>

Open MIDDLEWARE_HOME/user_projects/domains/domainName/config/fmwconfig/jps-config.xml in a text editor and make the following changes. (Note that these changes are also required if you deployed EPM System products to a domain hosted on another machine and the domain was not created with EPM System Configurator.)

To the <serviceInstances> set in the document, add the following:

<serviceInstances>
<serviceInstance provider="jaas.login.provider" name="idstore.loginmodule"> 
		<description>Identity Store Login Module</description>
		<property value="oracle.security.jps.internal.jaas.module.idstore.IdStoreLoginModule" name="loginModuleClassName" />
		<property value="REQUIRED" name="jaas.login.controlFlag" /> 
		<property value="true" name="debug" />
		<property value="true" name="addAllRoles" />
 </serviceInstance> 
<serviceInstance provider="idstore.ldap.provider" name="idstore.ldap"> 
...
 	<property name="virtualize" value="true"/>
</serviceInstance>
</serviceInstances>

To the jpsContexts/jpsContext section, add the following:
```
<serviceInstanceRef ref="idstore.loginmodule" />
```

(Optional) To simplify the startup of WebLogic servers, edit the boot.properties file on every server in the domain to provide the domain user and password. This file is located in MIDDLEWARE_HOME/user_projects/domains/domainName/servers/product/security.
Note:
Note that these inputs are stored in clear text until the servers are started, after which this data is encrypted by WebLogic.
To synchronize the password keys between the WebLogic Admin server machine and the managed server machine, copy SerializedSystemIni.dat from the WebLogic Admin server machine to the managed server machine; for example, WEBLOGIC_SERVER/user_projects/domains/EPMSystem/security) to DOMAIN_HOME/security where DOMAIN_HOME is the domain defined for the deployment in the MIDDLEWARE_HOME/user_projects/domains managed server home.

Start the WebLogic Administration Console and start the EPM System Web applications.

Note that when you manually deploy Web applications, use the start scripts in DOMAIN_HOME/bin.

Note:

If you didn't perform step step 20, you will be prompted to provide the domain user and password when you start the Web applications.

Tip:	You can also start Web applications on all machines using the Weblogic Administration Console. To do so, you must first run MIDDLEWARE_HOME/oracle_common/common/bin/setNMProps.sh(cmd) to modify nodemanager.properties.

During the managed server startup, the Shared Services Registry is updated with values for the EPM System Web applications you deployed.

Stop all EPM System Web applications.
Launch EPM System Configurator using the following command and select the “Configure Web Server” task.
Windows:
```
EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.bat
```
UNIX:
```
EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.sh
```
EPM System Configurator performs the registration with Shared Services and Configure Web Server tasks.
If you are also want to configure Essbase while you are manually deploying Web applications, when you first ran configtool-manual.sh, the Configure Essbase Server task was not available. It is available in this second pass of configuration, so if needed, select it now.

Start all EPM System services and Web applications according to the order described in Starting and Stopping EPM System Products. Note that when you manually deploy Web applications, use the start scripts in DOMAIN_HOME/bin.

Tip:	You can also start Web applications on all machines using the Weblogic Administration Console. To do so, you must first run MIDDLEWARE_HOME/oracle_common/common/bin/setNMProps.sh(cmd) to modify nodemanager.properties.

To validate the installation and verify deployment, see Validating the Installation and Verifying Deployment.

Tip:	If you need to redeploy a Web application after you have successfully deployed, replace the EAR file, delete the tmp folder for the managed server, and then start the application.