Configuring WebLogic

To configure WebLogic use the WebLogic Administration Console. By default the port number is 7001 and /console is the context root. Example: http://hostname:7001/console

Note: When selecting a menu option in the WebLogic Administrative Console, the names may differ depending on whether WebLogic is used in development mode or production mode.

Create a Machine

  1. Select Environment>Machines>New.
  2. Enter the name for the machine.
  3. If the OS is not UNIX, select Other from the Machine OS drop-down list.
  4. Click Next.
  5. Click Finish.

Create and Configure OIPA Server

Important: OIPA and the Web Application Utility can exist on the same WebLogic server if necessary.

Create the AdminConsole Server

  1. Select Environment>Servers.
  2. Click New.
  3. Enter AdminConsole for the name of the server.
  4. Set the listener port to a port that is not used by any other application.
  5. Click Next.
  6. Select Finish.

Add the AdminConsole Server to the Machine

  1. Select Environment>Machines.
  2. Select the machine that was created.
  3. Select the Servers tab.
  4. Select Add.
  5. Select the name of the Admin Console server created from the Select a server drop-down box.
  6. Click Finish.

Configure the Admin Console Server

  1. Select Environment>Servers.
  2. Select the Admin Console server that was created.
  3. Select the Server Start tab.
  4. Specify the class path. The path names will vary depending on the configuration

C:/Oracle/Middleware/Oracle_Home/wlserver/server/lib/weblogic.jar; folderpath/libs//commons-logging-1.2-9f99a00.jar;folderpath/conf/

Create Data Sources - Oracle

Create the Data Source for ADMINCONSOLEDS

  1. Select Services> Data Sources.
  2. In the configuration section on the right, click New and Select Generic Data Source.
  3. In the JDBC Data Source Properties pane that appears:
  4. Change the Name. This name can be anything, but has to be unique for the entire WebLogic server. If you have more than one OIPA instance on the server, then each instance should have a unique name.
  5. Change the JNDI Name to ADMINCONSOLEDS. This name cannot be anything other than ADMINCONSOLEDS.
  6. Select the Oracle database type.
  7. Click Next.
  8. Select the driver "*Oracle Driver (Thin XA) for Service Connections; Version:Any"
  9. Select Next.
  10. Select Next again when Transaction options are displayed.
  11. In the Connection Properties pane:
  12. Enter the Database Name.
  13. Enter the Host Name of the database server.
  14. Enter the Port number of the database server.
  15. Enter the Database user name. This can be obtained from the database administrator who installed the databases.
  16. Enter both password entries. This can be obtained from the database administrator who installed the databases.
  17. Select Next.

ac-oipa-jmxconnection-content.xml :

This ac-oipa-jmxconnection-content.xml file will have the ports to listen to cycle web servers. Based on count of cycle web managed servers , those many nodes should be created. port of this node should match with port that given in the cycle web arguments.

Cycle Web Server changes :

The below arguements should be added in arguments of cycle web each managed servers.

-Dcom.sun.management.jmxremote.port=5555

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.authenticate=false

-Dcom.sun.management.jmxremote.autodiscovery=true

-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

 

Important: The 5555 port can be anything which is not used by any other application in the server. Make sure this is open and available port. This port and the port in ac-oipa-jmxconnection-content.xml file should match.

 

Test if JMX port is publishing or not:

If the jmx server port is not exposed to jconsole or adminconsole, use the below argument in the WebLogic server arguments. IP adderess should be server actual IP address.

  • -Djava.rmi.server.hostname=ipaddress