To Configure BEA WebLogic Server as J2EE Container 2 on Protected Resource 2

After installing the bits, WebLogic Server must be configured for use as the J2EE container on Protected Resource 2.

Before You Begin

This procedure assumes you have just completed To Install BEA WebLogic Server as J2EE Container 2 on Protected Resource 2.

1. Run the WebLogic Server configuration script.

   # cd /usr/local/bea/weblogic92/common/bin # ./config.sh

2. When prompted, do the following:

   Select "Create a new Weblogic domain"	Click Next.
   Select "Generate a domain configured automatically to support the following BEA products:"	Click Next.
   Configure Administrator Username and Password	Enter the following and click Next.  Username: weblogic Password: w3bl0g1c
   Select "Prduction Mode" and "BEA Supplied JDK's" (Sun SDK 1.5.0_04@/usr/local/bea/jdk150_04)	Click Next.
   Customize Environment and Services Settings	Select yes and click Next.
   Configure the Administration Server	Accept the default values and click Next.
   Configure Managed Servers	Select Add, enter the following values, and click Next.  Name: ApplicationServer-2 Listen Port: 1081
   Configure Clusters	Accept the default values and click Next.
   Configure Machines	Select the Unix Machine tab, then select Add, type ProtectedResource-2, and click Next.
   Assign Servers to Machines	From the left panel select AdminServer ApplicationServer-2. From the right panel select ProtectedResource-2. Click --> and then click Next.
   Review WebLogic Domain	Click Next.
   Create WebLogic Domain	Add the following and click Create.  Domain name: ProtectedResource-2 Domain Location: /usr/local/bea/user_projects/domains (default)
   Creating Domain	Click Done.

3. Start the WebLogic administration server.

   # cd /usr/local/bea/user_projects/domains/ProtectedResource-2 # ./startWebLogic.sh

   When prompted, type the following credentials.

   Username

   weblogic

   Password

   w3bl0g1c

4. Run the netstat command to verify that the port is open and listening.

   # netstat -an | grep 7001 XXX.XX.XX.151.7001 *.* 0 0 49152 0 LISTEN XXX.X.X.1.7001 *.* 0 0 49152 0 LISTEN

   ---

   Note –

   You can also access the administration console by pointing a browser to http://protectedresource-2.example.com:7001/console.

   ---

5. Change to the AdminServer directory.

   # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/servers/AdminServer

6. Create a security directory and change into it.

   # mkdir security # cd security

7. Create a boot.properties file for the WebLogic Server administration server.

   The administrative user and password are stored in boot.properties. Application Server 2 uses this information during startup. WebLogic Server encrypts the file, so there is no security risk even if you enter the user name and password in clear text.

   # cat > boot.properties username=weblogic password=w3bl0g1c Hit Control D to terminate the command ^D

8. Restart the WebLogic administration server to encrypt the username and password in boot.properties.

   # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin # ./stopWebLogic.sh # ./startWebLogic.sh

9. Start the ApplicationServer-2 managed instance.

   # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin # ./startManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001

   You will be prompted for the following credentials.

   Username

   weblogic

   Password

   w3bl0g1c

10. Change to the ApplicationServer-2 directory.

    # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/ servers/ApplicationServer-2

11. Create a security directory and change into it.

    # mkdir security # cd security

12. Create a boot.properties file for the ApplicationServer-2 managed instance.

    The administrative user and password are stored in boot.properties. The WebLogic Server managed instance uses this information during startup. WebLogic Server encrypts the file, so there is no security risk even if you enter the user name and password in clear text.

    # cat > boot.properties username=weblogic password=w3bl0g1c Hit Control D to terminate the command ^D

13. Restart the managed server.

    # cd /usr/local/bea/user_projects/domains/ ProtectedResource-2/bin # ./stopManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001 # ./startManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001

14. Run the netstat command to verify that the port is open and listening.

    # netstat -an | grep 1081 XXX.X.X.1.1081 *.* 0 0 49152 0 LISTEN XXX.XX.XX.151.1081 *.* 0 0 49152 0 LISTEN

15. Access http://ProtectedResource-2.example.com:7001/console from a web browser.

16. Login to the BEA WebLogic Server as the administrator.

    Username

    weblogic

    Password

    w3bl0g1c

17. Click servers.

    On the Summary of Servers page, verify that both AdminServer (admin) and ApplicationServer-2 are running and OK.

18. Log out of the console.

19. Log out of the ProtectedResource–2 host machine.