Friday, 3 August 2012

deploying your first JAS server to new WLS and there are NO machines?

image

What a pain, don’t stress though.  The fix is super fast.

You’ll probably need to start your admin server, this will not start “out of the box” on a new install of wls

go searching for “startWebLogic.sh” in your middleware home dir.  You’ll find it a couple of times under the domain that you created.  Hopefully you’ve created one!

run the copy of startWebLogic.sh in bin32

Log into the weblogic console, probably with a URL something like:

http://webserver:7001/console

login with the weblogic user and password that you entered on install (if you are using an e1 server template I think its ovsadminE1)

You’ll get this totally awesome interface

image

Note that if you are ex-OAS – you might fall off your chair this interface is that cool!

goto environment, machines

image

press lock and edit

image

New

image

In our context, a machine is the logical representation of a computer that hosts one or more weblogic instances, so it makes sense to call your machine by it’s hostname!

image

Finish

image

Just remember your port number

image

Done, activate the changes

image

Bosch:  your server will now appear!  You’ll need to start the create new container wizard again in SM.

image

No comments:

Extending JDE to generative AI