A Manual Configuration of WebLogic Server

This chapter provides the detailed explanation about manual configuration of WebLogic server. Perform these steps only if you intend to configure the WebLogic server manually.

A.1 Overview

This section provides an overview of the manual configuration of WebLogic server:

The section includes:

• Creating a New Domain

• Configuring Memory options

• Configuring Machines

• Setting Up Commons Logging

• Configuring Servers

• Configuring JDBC Data Sources

• Configuring JMS Messaging Resources

• Configuring JMS Module Subdeployment

• Configuring the JMS Connection Factory

• Configuring a Notification Topic

• Configuring Queues

• Configuring Data Upload Size Limit

• Deploying Role Manager

A.1.1 Creating a New Domain

For Microsoft Windows:

Go to Start, Oracle WebLogic, WebLogic Server 10gR3, Tools, Configuration Wizard for W ebLogic 10.3.

For Linux:

1. Go to the WebLogic bin directory using the command:

   cd BEA_HOME/wlserver_10.3/common/bin for WebLogic 10.3
   

   Note:

   These instructions assume that the installation is a default installation performed with WebLogic server.

2. Start the Configuration Wizard using the following command:

   sh config.sh
   

3. In the Configuration Wizard:

   1. Select Create a New WebLogic domain and then click Next.

   2. Select Base this domain on an existing template. Click Next.

   3. Type the user name and the password, and then confirm the password for the domain. Click Next.

   4. On the left side of the window, select either Development Mode or Production Mode.

      Note:

      If WebLogic server is configured in production mode, you need to restart the ORMServer to login.

   5. On the right side of the window, select the appropriate JDK and then click Next.

      Note:

      If you are using your own JDK, ensure that it is the certified JDK for Oracle WebLogic server.

   6. A message is displayed asking whether you want to customize any of the options mentioned. Select No.

   7. The domain name and domain location are displayed by default. Click Create.

   8. Click Done.

A.1.2 Configuring Memory options

To configure memory options:

• For Microsoft Windows systems

  Edit the startManagedWebLogic.cmd script and specify memory options as follows:

  Follow the format:

  %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS%

  Locate the following line:

  set JAVA_OPTIONS=%JAVA_OPTIONS% -XnoOpt

  Before this line, add the following if using Sun Java Virtual Machine (JVM):

  set MEM_ARGS=-Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m

  Add the following if using JRockit Java Virtual Machine (JVM):

  set MEM_ARGS=-Xms1280m -Xmx1280m

  Note:

  The -XnoOpt option turns off adaptive optimization and is required for stable Oracle Role Manager operation.

• For UNIX Systems

  Edit the startManagedWebLogic.sh script and specify memory options as follows:

  Locate the line that starts with the following:

  $JAVA_HOME/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}

  If using Sun Java Virtual Machine (JVM), add the following line before this line:

  MEM_ARGS="-Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m"

  export MEM_ARGS

  If using JRockit Java Virtual Machine (JVM), add the following line before this line:

  MEM_ARGS="-Xms1280m -Xmx1280m"

  export MEM_ARGS

  JAVA_OPTIONS="$JAVA_OPTIONS -XnoOpt"

  export JAVA_OPTIONS

Note:

The -XnoOpt option turns off adaptive optimization and is required for stable Oracle Role Manager operation.

A.1.3 Starting WebLogic Server

To start the Oracle WebLogic server:

For Microsoft Windows:

1. For WebLogic 10.3, go to Start, Oracle WebLogic, User Projects, Domain Name, and then click Start Admin Server for WebLogic Server Domain.

2. Log on to the WebLogic Server Administration Console by using your new account and by pointing a Web browser to the following URL:

   http://hostname:7001/console

For Linux:

1. Go to the WebLogic user_projects/domains directory, for example:

   cd BEA_HOME/user_projects/domains/

2. Go to the directory of the domain that you just created using the Configuration Wizard. For example, cd domain name.

3. Start the BEA WebLogic server using the following command:

   sh startWebLogic.sh
   

4. Log on to the WebLogic Server Administration Console by using your new account and by pointing a Web browser to the following URL:

   http://hostname:7001/console

A.1.4 Configuring Machines

A machine is a host that runs a WebLogic Server instance. You can configure a machine using the WebLogic Server Administration Console.

To configure a machine:

1. Select Machines under Environment and then click New.

2. In the Name field, type a name for the machine.

3. In the Machine OS field, select the operating system.

4. Click OK.

To start the node manager:

Use the following steps to start the node manager:

1. Navigate to WebLogic_install_dir/server/bin

2. Run the startNodeManager.cmd command for Microsoft Windows.

3. Run the startNodeManager.sh command for Linux.

A.1.5 Configuring Servers

Note:

WebLogic server must be already installed on which Role Manager application is configured.

The server is the machine that hosts the application. Use the following steps to configure a server in the WebLogic Server Administration Console:

To configure a server:

1. Select Servers under Environment and then click New.

2. In the Server Name field, type the name of the Role Manager server, for example ORMServer.

3. In the Server Listen Address field, type the IP address of the server.

4. In the Server Listen Port field, type the Role Manager listening port number .

5. Specify whether the server should belong to a cluster.

6. Click Next. Review your choices and then click Finish.

To assign a machine to the server:

1. Click the newly created server from the table of servers.

2. Click the Configuration tab and then click the General subtab.

3. In the Machine field, type the machine name.

4. Click Save.

To start the server:

1. Select Servers under Environment, and then click the newly created server from the table of servers.

2. Click the Control tab, then click the Start/Stop subtab.

3. Select ORMServer and then click Start.

A.1.6 Setting Up Commons Logging

Setting up Commons Logging for Oracle Role Manager on WebLogic 10.3 involves creating a new Log4j appender, adding jars to ORM_WLS_DOMAIN_HOME/lib and adding JAVA_OPTION in startManagedWebLogic.cmd for Microsoft Windows and startManagedWebLogic.sh for Linux.

To Set Up Commons Logging:

1. Create a new file, log4j.properties in ORM_WLS_DOMAIN_HOME for example, BEA_HOME/user_projects/domains/orm_domain:

   log4j.rootLogger=debug, ORM
    
   log4j.logger.oracle.iam.rm=debug
   log4j.logger.oracle.iam.rm.persistence=INFO
   log4j.logger.org.springframework=INFO
   log4j.logger.org.apache=WARN
   log4j.logger.org.quartz=WARN
    
   # Uncomment all these stdout lines if logs are desired on console
   #log4j.appender.stdout=org.apache.log4j.ConsoleAppender
   #log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
   #log4j.appender.stdout.layout.ConversionPattern=%5p [%d] %t %c (%F:%L) - %m%n
   #log4j.appender.stdout.threshold=info
    
   log4j.appender.ORM=org.apache.log4j.RollingFileAppender
   log4j.appender.ORM.File=C:/bea/user_projects/domains/orm_domain/servers/ORMServer/logs/ORM.log
   # Change the threshold to INFO for less verbose logging
   log4j.appender.ORM.threshold=debug
   log4j.appender.ORM.MaxFileSize=1024KB
   # Keep backup files
   log4j.appender.ORM.MaxBackupIndex=5
    
   log4j.appender.ORM.layout=org.apache.log4j.PatternLayout
   log4j.appender.ORM.layout.ConversionPattern=%5p [%d] %t %c (%F:%L) - %m%n
   

2. In the file ORM_WLS_DOMAIN_HOME/bin/startManagedWebLogic.cmd, add a new line after line 55:

   @REM. Set JAVA_OPTIONS to the java flags that you want to pass to the vm.

   set JAVA_OPTIONS=%JAVA_OPTIONS% -Dlog4j.configuration=file:C:/bea/user_projects/domains/orm_domain/log4j.properties
   

   Replace "C:/bea" with BEA_HOME.

3. Add the following jars into ORM_WLS_DOMAIN_HOME/lib folder:

   • commons-logging-1.0.4.jar (download from apache.org)

   • log4j-1.2.8.jar (download from apache.org)

4. Restart ORM WebLogic server and you see ORM debug messages in the log-file:

   BEA_HOME/user_projects/domains/orm_domain/servers/ORMServer/logs/ORMServer.log

A.1.7 Configuring JDBC Data Sources

To configure the non-XA data source:

1. In the Domain tree, select Services, JDBC, Data Sources.

2. Click New. The JDBC Data Source Properties page appears.

3. In the Name field, type the name of the data source, for example, ORM Data Source.

4. In the JNDI Name field, type the JNDI path :

   orm/jdbc/ORMServerDS

5. From the Database Type list, select Oracle.

6. From the Database Driver list, select Oracle's Driver (Thin).

7. Click Next and deselect Supports Global Transactions.

8. Click Next. The Connect Properties page appears.

9. In the Database Name field, type the name of the database, for example, (Oracle SID).

10. In the Host Name field, type the host name or IP address of the machine hosting the database.

11. In the Port field, type the port number on which the database is listening, for example, 1521.

12. In the Database User Name field, type the database user name that was created in the Step 3 of the "Creating the Role Manager Users" section.

13. In the Password field, type the password for the database user and in the Confirm Password field, retype the password.

14. Click Next. The Test Database Connection page appears.

15. Verify the contents.

16. Click Next. The Select Targets page appears.

17. Select ORMServer as the target and then click Finish.

To configure the XA data source:

1. In the Domain tree, select Services, JDBC, Data Sources.

2. Click New. The JDBC Data Source Properties page appears.

3. In the Name field, type the name of the data source, for example, ORM XA Data Source.

4. In the JNDI Name field, type the JNDI path :

   orm/jdbc/ORMServerXADS

5. From the Database Type list, select Oracle.

6. From the Database Driver list, select Oracle's Driver (Thin XA).

7. Click Next.

8. The Transaction Options page appears. Click Next.

9. In the Database Name field, type the name of the database, for example, (Oracle SID).

10. In the Host Name field, type the host name or IP address of the machine hosting the database.

11. In the Port field, type the port number on which the database is listening, for example, 1521.

12. In the Database User Name field, type the database user name that was created in the Step 3 of the "Creating the Role Manager Users" section.

13. In the Password field, type the password for the database user and in the Confirm Password field, retype the password.

14. Click Next. The Test Connection Database page appears.

15. Verify the contents.

16. Click Next. The Select Targets page appears.

17. Select ORM server as the target and then click Finish.

    Note:

    If you are using RAC database, provide the following string while creating the data source:

    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=host1-vip)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2-vip)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl.us.oracle.com)))
    

A.1.8 Configuring JMS Messaging Resources

To configure the JMS Server:

1. In the domain tree, select Services, Messaging, JMS Servers.

2. Click New. The JMS Server Properties page appears.

3. In the Name field, type the name of the Role Manager JMS Server, for example, ORM JMSServer.

4. Click Next. The Select targets page appears.

5. In the Target field, select ORMServer as the target and then click Finish.

To configure the JMS Module:

1. In the domain tree, select Services > Messaging > JMS Modules.

2. Click New. The Create JMS System Module page appears.

3. In the Name field, type the name of the Role Manager JMS module, for example, ORM JMSModule.

4. Click Next. The Target page appears.

5. In the Target field, select ORMServer as the target and then click Next.

6. Click Finish.

A.1.9 Configuring JMS Module Subdeployment

To configure JMS Module Subdeployment:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMS Module, for which you want to configure the subdeployment. Click the Subdeployments tab.

3. Click New. The Subdeployment Properties page appears.

4. In the Name field, type the name of the subdeployment, for example, ORM JMSSubdeployment.

5. Click Next. The Target page appears.

6. Select ORM JMSServer as the JMS server target and then click Finish.

A.1.10 Configuring the JMS Connection Factory

To configure a JMS Connection Factory:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMSModule.

3. Click New under Summary of Resources.

4. Select Connection Factory from the list of JMS resources.

5. Click Next. The Connection Factory Properties page appears.

6. In the Name field, type the name for the connection factory, for example, ORM ConnectionFactory.

7. In the JNDI Name field, type the path for the connection factory, for example, orm/jms/ConnFac.

8. Click Next and then click Finish.

9. In the domain tree, select Services, Messaging, JMS Modules.

10. Click ORM JMSModule.

11. Click ORM Connection Factory.

12. Navigate to the Configuration tab, Transactions sub-tab.

13. Select the XA Connection Factory Enabled check box.

14. Click Save.

To configure a Finalization Connection Factory:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMSModule.

3. Click New under Summary of Resources.

4. Select Connection Factory from the list of JMS resources.

5. Click Next. The Connection Factory Properties page appears.

6. In the Name field, type the name for the connection factory, for example, Finalization ORM ConnectionFactory .

7. In the JNDI Name field, type the path for the connection factory, for example, orm/jms/FinalizationConFac.

8. Click Next, and then click Finish.

9. In the domain tree, select Services, Messaging, JMS Modules.

10. Click ORM JMSModule.

11. Click Finalization ORM ConnectionFactory.

12. Navigate to the Configuration tab, Transactions sub-tab.

13. Select the XA Connection Factory Enabled check box.

14. Click Save.

A.1.11 Configuring a Notification Topic

To configure a notification topic:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMS Module.

3. Click New under Summary of Resources.

4. Select Topic from the list of JMS resources.

5. Click Next. The JMS Destination Properties page appears.

6. In the Name field. type a name for the topic, for example, ORM NotificationTopic.

7. In the JNDI Name field, type the path for accessing the topic, for example, orm/topic/NotificationTopic.

8. In the Template field, select None.

9. Click Next.

10. Select ORM JMSSubdeployment that you created in the Step 4 of the "Configuring JMS Module Subdeployment" section from the list.

11. Click Finish.

A.1.12 Configuring Queues

To configure the ORM Finisher Queue:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMS Module.

3. Click New under Summary of Resources.

4. Select Queue from the list of JMS resources.

5. Click Next. The JMS Destination Properties page appears.

6. In the Name field, type a name for the queue, for example, ORM FinisherQueue.

7. In the JNDI Name field, type the path for accessing the topic as orm/queue/BtFinisherQueue.

8. In the Template field, select None.

9. Click Next.

10. Select ORM JMSSubdeployment that you created in the Step 4 of the "Configuring JMS Module Subdeployment" section from the list.

11. Click Finish.

To configure the ORM Loader Queue:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMS Module.

3. Click New under Summary of Resources.

4. Select Queue from the list of JMS resources.

5. Click Next. The JMS Destination Properties page appears.

6. In the Name field, type a name for the queue, for example, ORM LoaderQueue.

7. In the JNDI Name field, type the path for accessing the topic as orm/queue/LoaderQueue.

8. In the Template field, select None.

9. Click Next.

10. Select ORM JMSSubdeployment that you created in the Step 4 of the "Configuring JMS Module Subdeployment" section from the list.

11. Click Finish.

To configure the ORM Incoming Event Queue:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMS Module.

3. Click New under Summary of Resources.

4. Select Queue from the list of JMS resources.

5. Click Next. The JMS Destination Properties page appears.

6. In the Name field, type a name for the queue, for example, ORM IncomingEventQueue.

7. In the JNDI Name field, type the path for accessing the topic as orm/queue/IncomingEventQueue.

8. In the Template field, select None.

9. Click Next.

10. Select ORM JMSSubdeployment that you created in the Step 4 of the "Configuring JMS Module Subdeployment" section from the list.

11. Click Finish.

A.1.13 Configuring Data Upload Size Limit

You can upload a DAR file to load data of maximum size 10 MB into the system. If you try to load data larger than this maximum upload size limit, you get an error message. You can configure the maximum data upload size limit to a higher or lower value than the default settings.

To configure the data upload size limit:

1. Go to Environment, Servers, ORM Server.

2. On the Configuration tab, click the Server Start subtab.

3. In the Arguments field, append the following argument to the new value.

   -Doracle.iam.rm.loader.max_upload_size=<new value>
   

   For example:

   -Doracle.iam.rm.loader.max_upload_size=1073741824
   

4. Click Save.

A.1.14 Creating the Oracle Role Manager User

Before installing the WebLogic server application, you must perform the following steps in the security realm:

1. Go to Security Realms and click the realm name, for example, myrealm.

2. Click Users and Groups and then Users.

3. Click New and then type the following details:

   1. In the Name field, type ormserver.

   2. In the Description field, type the description, for example, principal that acts as ORM Server.

   3. In the Password field, type the password, for example, ormserver.

4. Click OK.

5. Click the newly created user, for example, ormserver.

6. To add the created user to the Deployers group:

   1. Go to the Groups tab.

   2. From the Available list, select Deployers.

   3. Click the right-pointing arrow.

   4. Click Save.

A.1.15 Deploying Role Manager

If you have already deployed the Role Manager server earlier and removed it and then try to deploy again, the deployment is delayed. This is because, the error messages related to the previous unsuccessful attempts of installation gets queued up in the log file and delays the deployment procedure. To prevent such delay, perform the following steps before you actually deploy the Role Manager server:

Note:

Perform this procedure only if you are repeating the deployment of the same Role Manager server.

1. Start up the Role Manager server that contains the JMS server.

2. Navigate to Services, Messaging, and JMS Modules.

3. Click ORM JMSModule.

4. From the resource list, select the ORMFinisherQueue.

5. On the Monitoring tab, select the ORM JMSModule! ORM Finisher Queue destination and click Show Messages.

6. Click Delete and from the list of options, select Delete All.

7. In the confirmation page, click Yes.

To deploy the Role Manager server application:

1. Select Deployments in the left part of the Administration Console window.

2. Click Install in the right part of the Administration Console window.

3. In the ORM_HOME, navigate to the server.ear file and select it. Click Next.

   Note:

   The server.ear file can be accessed from the path ORACLE_HOME/lib/server.ear.

4. Select Install this deployment as an application. Click Next.

5. Select ORM Server as the target in the Target field. Click Next.

6. In the Name field, type the name of the Role Manager server application, for example, ORM ServerApp.

7. Click Next and in the Install Application Client page, click Finish.

   Note:

   You must restart the ORMServer to login.

8. Click Save to activate the changes.

9. To test the server installation, ensure that you can get to the Role Manager administrative console from a Web browser. For example:

   http://localhost:<port>/ormconsole

   Note:

   By default 7001 is the port for admin server and 5556 is the port for NodeManager.

   You should be able to see the Home page of the Role Manager administrative console.

To start the server application for WebLogic 10.3:

Starting the server application is automatically taken care for WebLogic 10.3.

To deploy the Role Manager Web application:

1. Select Deployments in the left part of the Administration Console window.

2. Click Install in the right part of the Administration Console window.

3. Navigate to the webui.war file and select it. Click Next.

   Note:

   The webui.war file can be accessed from the path ORACLE_HOME//webui/weblogic/10.3/webui.war.

4. Select Install this deployment as an application. Click Next.

5. In the Target field, select ORMServer as the target and then click Next.

6. In the Name field, type the name of the Web user interface application.

7. Select Custom Roles and Policies: Use only roles and policies that are defined in the Administration Console from the Security list.

8. Click Next and then click Finish.

9. Test the Web application installation as follows:

   1. In an Internet Explorer 6 or 7, navigate to the Role Manager Web application address. For

      example:

      http://localhost:<port>/webui

   2. Log in as the Role Manager Administrator created in "Installing Role Manager".

      Note:

      Data must be loaded into the system to expose all the functionality of the application. Refer to "Loading Standard and Sample Data" for instructions.

      You should be able to see the Home page of the Role Manager Web application.

To start the Web application for WebLogic 10.3:

Starting the Web application is automatically taken care for WebLogic 10.3.