Oracle HTTP Server 12c starting component with Nodemanager
Welcome back
configuring the OHS 12 domain using the Configuration Wizard, there does not seem to be an option to specify a different Node manager port. It uses the default 5556, where it is already used by FMW Domain[SOA Domain or WebLogic Domain].
Following steps are used to modify and use alternative Nodemanager port in a standalone OHS domain.
Navigate to as shown below:
Edit the config.xml file Look for the following node-manager tag block
Change this code block it by adding listen-port tag to the Node Manager port same value as given in step 1.
Now start the components.
Then you can check the url that can connect to the ohs instance and shows below...
http://localhost:7777
Stop the OHS server from Command line
Before you run the stopComponent.sh script to stop OHS you must check that Node manager for OHS must be running.
cd $OHS_DOMAIN/bin/
./stopComponent.sh ohs1
OHS 12.2.1 Silent installation
Uninstall OHS 12c
Configuring OHS 12c domain
OHS 12c instance Start/Stop
Oracle Traffic Director 12.2.1 Silent Installation
OHS Getting started
OHS 12c Using alternate Node managr port
configuring the OHS 12 domain using the Configuration Wizard, there does not seem to be an option to specify a different Node manager port. It uses the default 5556, where it is already used by FMW Domain[SOA Domain or WebLogic Domain].
Following steps are used to modify and use alternative Nodemanager port in a standalone OHS domain.
- Open the nodemanager.properties, change the Node Manager port (default 5556) to a port that is currently not in use. change port here from 5556 to 5566 and then Save this file.
- Modify the OHS domain's config.xml. This is a new step for 12c environments!
Node Manager properties for OHS Domain |
Navigate to as shown below:
cd $OHS_DOMAIN/config
Edit the config.xml file Look for the following node-manager tag block
localmachine localhost {AES}/TU+/JiP22JJzuRa7Rqpp1xQkgPTmQ4Sb/VvBHJWPhg=
Change this code block it by adding listen-port tag to the Node Manager port same value as given in step 1.
localmachine localhost 5566 {AES}/TU+/JiP22JJzuRa7Rqpp1xQkgPTmQ4Sb/VvBHJWPhg=
Now start the components.
cd $OHS_DOMAIN/bin nohup ./startNodeManager.sh 2>&1 & ./startComponent.sh ohs1
Starting OHS domain |
Then you can check the url that can connect to the ohs instance and shows below...
http://localhost:7777
Stop the OHS server from Command line
Before you run the stopComponent.sh script to stop OHS you must check that Node manager for OHS must be running.
cd $OHS_DOMAIN/bin/
./stopComponent.sh ohs1
stopComponent ohs1 using Commandline |
Reference
OHS Getting started
Comments
Post a Comment