Starting and Accessing OAM

After you have successfully OAM and configured it, you can start it by following this procedure.
1. ssh to the host server. 
2. Start Weblogic Admin console

# cd /opt/app/middleware/projects/domains/uatoam_domain
# ./startWeblogic.sh

You are going to get prompt with admin credential. 

You can then end the process by pressing Ctrl + C

3. Add security boot.properties file so you will not be prompt with credential the next time. 

# cd /opt/app/middleware/projects/domains/uatoam_domain/servers/AdminServer 
# mkdir security
# cd security 
# vi boot.properties

  username=<username>
  password=<password> 

  Note: substitute with the same credential you have entered above. This file will be encrypted by weblogic the next time it starts. 

# cd /opt/app/middleware/projects/domains/uatoam_domain
# ./startWeblogic.sh &

Note: the & is an indication that the process can run in the background when it is escaped. 

Also take a note that this time around you will not be prompt with a password anymore. When weblogic starts, it checks for the boot.properties file.

You cannot escape the process by pressing any key.

4. Accessing the Admin Server

Open a browser, http://<host>:7001/console

Note: port 7001 is default. Use the one that you input during the install.

http://<server_name>:7001/console 

 After login, you will prompt with landing page. 

 
5. Start Node Manager

Edit node.properties to allow Admin console to start Managed servers.
# cd /opt/app/middleware/wls_home/common/nodemanager
# vi node.properties 

edit value for StartScriptEnabled from false to true.

 






Save file. 

# cd /opt/app/middleware/wls_home/server/nodemanager
# ./startNodeManager.sh &


6. Start Managed Servers

Thru command prompt: 

# cd /opt/app/middleware/projects/domains/uatoam_domain/bin 
# ./startManagedWebLogic.sh oam_server1

Again you will be prompt with admin credential. 

Note: This may take a while to start for the first time. 

You can then end the process by pressing Ctrl + C
 
add security boot.properties file so you will not be prompt with credential the next time.

# cd /opt/app/middleware/projects/domains/uatoam_domain/servers/oam_server1
# mkdir security
# cd security 
# vi boot.properties

  username=<username>
  password=<password> 

  Note: substitute with the same credential you have entered above. This file will be encrypted by weblogic the next time it starts. 

# cd /opt/app/middleware/projects/domains/uatoam_domain
# ./startManagedWebLogic.sh oam_server1 &

Thru admin console:

Login to admin console, refer to instructions above.

From Landing page, click on Servers.

   
Under control tab, select the server then click "Start"

Select "yes"

   
















State should change from "Starting" to "Running"

7. Accessing OAM Server

From the browser, you can access to oam console thru

http://<host>:14100/oamconsole

Note: you can only access the oam console if the server is started. 

After successful authentication, you will get to the landing page.

Move on to the next section of this blog.... Configure OAM policy and system configuration.