OHS12c: Different ways of start/stop OHS instance services

We can start/stop the ohs instance in different ways. Here are the few ways...

1. By using WLST

• Connect to WLST
• Connect to nmConnect()
• Run the below command(s).
• START -    start('ohs1')  [or]   nmStart(serverName='ohs1', serverType='OHS')
• STOP    -    shutdown('ohs1')
• RESTART -  softRestart('ohs1')
• STATUS      - state('ohs1')

2. By using command line

•     Go to Domain location & run the below .sh scripts.
• START - $DOMAIN_HOME/bin/startComponent.sh ohs1
• STOP -    $DOMAIN_HOME/bin/stopComponent.sh ohs1

Also we can start/stop from EM (Enterprise Manager). 

• Login to EM & then select corresponding Weblogic Domain name. 
• Select machine host to be associated to corresponding OHS instance and then start/stop the corresponding instance.

Note: There are so many WLST locations available in your setup depending up on installed FMW components. Make sure to start WLST script from $ORACLE_HOME/ohs/common/bin directory. 

OHS12c - Update the ohs instance level configurations

As OHS12c is associated with Weblogic server and if the corresponding Weblogic setup as per EDG (Enterprise Deployment Guide) then you have to follow below guidelines if you are updating OHS configurations.

1. Make sure to update the configurations at aserver path (i.e. Admin Server location) and restart Admin Server. Then the changes will be propagated to mserver path (i.e. Managed Server/OHS instance locations)
2. If you directly apply any change at mserver path, then those changes will available till you restart the Admin Server. 
3. After that your Admin Serer will propagate the Admin Server copies of httpd.conf, mod_wl_ohs.conf/other all configurations to mserver path. As a result your local changes which are available at mserver path will be lost.

Conclusion: Make sure to update the configurations at aserver path.

OHS12c: Admin port conflict issue while configuring the new instance.

• There are 2 options available while installing OHS.
• Collocated HTTP Server
• Standalone HTTP Server
• At the time of configure OHS, below screen appear in the middle of configurations. 

• In the above screen, we should not use Weblogic Server Admin & Port information. This is specific to OHS Configurations and have to use local sever info (other than Weblogic Admin Server Port). 
• If we use Admin server info & if already Admin Sever is running then will get below error stack ( If we start OHS Instance).
• [2015-06-12T04:22:23.3124-04:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c] [host_id: My_OHS_Server1] [host_addr: 10.25.11.6] [pid: 25178] [tid: 140568266618688] [e_sock: could not bind to address 10.25.11.10:7001
• [2015-04-12T04:22:23.3124-04:00] [OHS] [INCIDENT_ERROR:20] [OHS-9999] [worker.c] [host_id: My_OHS_Server1] [host_addr: 10.25.11.6] [pid: 25178] [tid: 140568266618688] [ shutting down
• [2015-04-12T04:22:23.3124-04:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: My_OHS_Server1] [host_addr: 10.25.11.6] [pid: 25178] [tid: 140568266618688] [user: oracle ..
• Make sure have other port info other than Admin server info. 
• If you have already used Admin info then try to modify the configuration at OHS configuration files and start OHS instance.

Finally OHS instance will come into normal state.