Starting and Stopping the Essbase Server 11.1.2 using OPMN (Doc ID 1114453.1)

Starting and Stopping the Essbase Server 11.1.2 using OPMN (Doc ID 1114453.1) To BottomTo Bottom In this Document Purpose Scope Details Why use OPMN with Essbase : Methods to start the Essbase server using the OPMN: 1- Use these commands to start and monitor Essbase from OPMN: 2- Windows Start Menu Command: 3- Windows Startup Script: 4- UNIX Startup Script: To stop Essbase Server using the OPMN: 1) Command line: 2- Windows Stop Script: 3- UNIX Stop Script: Starting and Stopping Essbase without using OPMN: To start the Essbase server without using the OPMN: To stop the Essbase server without using the OPMN: 1- Stopping via Administration Services Console: 2- Stopping Essbase via MaxL: 3- Stopping Essbase via ESSCMD: 4- Agent: Common Issues References APPLIES TO: Hyperion Essbase - Version 11.1.2.0.00 to 11.1.2.0.00 [Release 11.1] Information in this document applies to any platform. ***Checked for relevance on 17-May-2013*** PURPOSE How to start, stop, monitor and control the Essbase Agent process. SCOPE Possible ways for monitoring and controlling the Essbase Agent process. DETAILS There are two possible ways for monitoring and controlling the Essbase Agent process. - Starting and Stopping Essbase using OPMN. - Starting and Stopping Essbase without using OPMN. Why use OPMN with Essbase : The Oracle Process Manager and Notification server (OPMN) enables you to monitor and control the Essbase Agent process. You have to add Essbase Agent information to the opmn.xml file to enable the OPMN to start, stop, and restart the agent using the OPMN command line interface. The OPMN can automatically restart the Essbase Agent when it becomes unresponsive, terminates unexpectedly, or becomes unreachable as determined by ping and notification operations. During the EPM installation, EPM System Installer installs OPMN and registers Essbase Server for OPMN. The OPMN manages the Essbase Agent, which manages the Essbase Server. Methods to start the Essbase server using the OPMN: 1- Use these commands to start and monitor Essbase from OPMN: opmnctl status Enables you to determine the status of system component processes. opmnctl startproc ias-component=EssbaseInstanceName Starts the system component named EssbaseInstanceName* opmnctl restartproc ias-component=EssbaseInstanceName Restarts the system component named EssbaseInstanceName* *) EssbaseInstanceName: - If you did not implement failover clustering, EssbaseInstanceName is the name of the Essbase instance that you entered when you configured Essbase Server in the Essbase Server Configuration page during configuration process with EPM System Configurator. - If you implemented failover clustering, EssbaseInstanceName is the name of the Essbase cluster that you entered when you set up the Essbase cluster. Note: The Components that are managed by OPMN should never be started or stopped manually. Use the opmnctl command line utility to start and stop system components. 2- Windows Start Menu Command: Select Start --> Programs --> Oracle EPM System --> Essbase --> Essbase Server --> Start Essbase This command launches startEssbase.bat and redirects to OPMN. Note: The registered Service Name is: opmn_instanceName and the Display Name in Windows Services Control Panel is: Oracle Process Manager (instanceName) 3- Windows Startup Script: - Go to this path: MIDDLEWARE_HOME/user_projects/epmsystem1/bin/startEssbase.bat - Click on the startEssbase.bat to start the Essbase server and redirect to OPMN. Note: If you have more than one Essbase instance, then each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase, startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this location to launch this instance of Essbase. --> ESSCMD: MIDDLEWARE_HOME/user_projects/epmsystem1/EssbaseServer/EssbaseServerInstanceName/bin/startEsscmd.bat It is also available in the /EssbaseClient directory. -->ESSMSH: MIDDLEWARE_HOME/user_projects/epmsystem1/EssbaseServer/EssbaseServerInstanceName/bin/startMaxl.bat It is also available in the /EssbaseClient directory. All the scripts call setEssbaseEnv.bat to set up ESSBASEPATH, ARBORPATH, and PATH before starting. 4- UNIX Startup Script: - Go to this path: (It redirects to OPMN) MIDDLEWARE_HOME/user_projects/epmsystem1/bin/startEssbase.sh - Click on the startEssbase.sh to start the Essbase server and redirect to OPMN. Note: If you have more than one Essbase instance, then each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase, startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this location to launch this instance of Essbase. --> ESSCMD: MIDDLEWARE_HOME/user_projects/epmsystem1/EssbaseServer/EssbaseServerInstanceName/bin/startEsscmd.sh It is also available in the /EssbaseClient directory. --> ESSMSH: MIDDLEWARE_HOME/user_projects/epmsystem1/EssbaseServer/EssbaseServerInstanceName/bin/startMaxl.sh It is also available in the /EssbaseClient directory. - All the scripts call hyperionenv.doc to set up ESSBASEPATH, ARBORPATH, and PATH before starting. - When running Essbase manually from a console, the console cannot be set to UTF-8 encoding. - There is another instance of startEssbase.sh located in this path: MIDDLEWARE_HOME/user_projects/epmsystem1/EssbaseServer/essbaseserver1/bin. This file does not redirect to OPMN. - You must use this startEssbase.sh file to start Essbase if Oracle Business Intelligence Enterprise Edition is the data source for Essbase. To stop Essbase Server using the OPMN: If you started the Essbase Server using the OPMN, then you have to use OPMN to stop it, using one of the following methods: 1) Command line: opmnctl stopproc ias-component=EssbaseInstanceName Stops the system component named EssbaseInstanceName Note: If you attempt to use MaxL to shut down an Essbase instance that was started using OPMN, you are warned to use OPMN to shut down Essbase. - Stopping Essbase Server can take some time, depending on how many Essbase applications are running on the server. To stop the Essbase Server, you need Administrator permissions. 2- Windows Stop Script: MIDDLEWARE_HOME/user_projects/epmsystem1/bin/stopEssbase.bat It redirects to OPMN. 3- UNIX Stop Script: MIDDLEWARE_HOME/user_projects/epmsystem1/bin/stopEssbase.sh It redirects to OPMN. Starting and Stopping Essbase without using OPMN: Oracle provides an alternate method of starting Essbase that does not use OPMN. To start the Essbase server without using the OPMN: - Go to this instance of startEssbase.sh located in: MIDDLEWARE_HOME/user_projects/epmsystem1/EssbaseServer/essbaseserver1/bin - Click on the startEssbase.sh to start the Essbase server. Note: If you use this method of starting Essbase, then the OPMN is not used for managing Essbase and active-passive failover clusters are not supported. To stop the Essbase server without using the OPMN: If you used this alternate method to start Essbase, use one of the following methods to stop Essbase: 1- Stopping via Administration Services Console: In the Enterprise View--> right-click the Essbase Server node --> Select Stop. 2- Stopping Essbase via MaxL: Use this MaxL command: alter system shutdown; Example: login admin 'password' on local; alter system shutdown; 3- Stopping Essbase via ESSCMD: Use this ESSCMD command: SHUTDOWNSERVER servername username password Where: servername: Host name associated with the Essbase Server you want to shut down. username: Your user name. password: Your password. Example: shutdownserver local admin password; 4- Agent: If you started Agent in the foreground, you can use the quit command: quit; Common Issues See: Document 1277055.1 for a number of common issues and solutions when using Essbase with OPMN Document 1179893.1 for a problem when signing off from a remote HSS Server (will affect Essbase login) Document 1156592.1 for a problem when signing off from a remote Essbase Server Document 1272837.1 for installing a second Essbase Server instance on the same physical machine REFERENCES NOTE:1156592.1 - Essbase Service Fails After Being Started from Remote Desktop Client. OPMN.exe NOTE:1179893.1 - Oracle Epm 11.1.2 Crashed After Signing Off From Remote Server Using The Account Which Installed EPM Services NOTE:1272837.1 - Install a Second Essbase Instance on the Same Server in Essbase 11.1.2 NOTE:1277055.1 - Troubleshooting Essbase Issues With Oracle Process Manager and Notification (OPMN) server