Managing Middleware using Enterprise Manager (MOSC)

MOSC Banner

Nodemanager as a service via OEM deployment procedure

edited Jan 29, 2014 10:41AM in Managing Middleware using Enterprise Manager (MOSC) 5 commentsAnswered ✓
I am trying to use OEM12c  to clone a WebLogic 12c domain. The new domain will include two machines with 2 managed servers on each machine. I want nodemanager to run as a service on both of the machines in the domain. The procedure forces me to configure nodemanager to listen on a different port on each machine in the domain. If nodemanager is running as a service on each machine why does OEM force me to use different port numbers.

I'm using the default "Provision Middleware" procedure in OEM. Is there another procedure that assumes nodemanager is running as a service? What is Oracle recommendation as to how to run nodemanager? Is there thorough documentation on creating custom procedures?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center