Oracle Weblogic Server (MOSC)

MOSC Banner

Configuration of OHS has wrong username since moving from 12.2.1.3 to 12.2.1.4

A question: how does one go about changing the "default" username that OHS automatically expects to receive when starting from the console?

A new installation of a WebLogic application has been (mostly successfully) stood up on a new host in our environment, transitioning from an older 12.2.1.3 setup to one with 12.2.1.4. However, setting up OHS has run into some problems - specifically with the credentials. The Node Manager and WebLogic admin servers both start up, and the WebLogic admin server now successfully refers to boot.properties settings.

However, though it originally was (and still is) able to start through Enterprise Manager, OHS has not been capable of starting from the command line. No boot.properties file setups appear to affect this startup process or the credentials necessary, and attempting to start OHS manually from the console skips over the username and straight to the password. According to the readout when OHS fails to start it is looking for user 'mFO7v3ZbUY' instead of user 'adminuser'. This username string also appears in the newer config.xml file; where <node-manager-username> shows 'adminuser' and <node-manager-password-encrypted> shows {AES}aCyphertextString in the 12.2.1.3 setup, the 12.2.1.4

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center