After installing the bits, WebLogic Server must be configured for use as the J2EE container on Protected Resource 2.
This procedure assumes you have just completed To Install BEA WebLogic Server as J2EE Container 2 on Protected Resource 2.
Run the WebLogic Server configuration script.
# cd /usr/local/bea/weblogic92/common/bin # ./config.sh |
When prompted, do the following:
Start the WebLogic administration server.
# cd /usr/local/bea/user_projects/domains/ProtectedResource-2 # ./startWebLogic.sh |
When prompted, type the following credentials.
weblogic
w3bl0g1c
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 |
You can also access the administration console by pointing a browser to http://protectedresource-2.example.com:7001/console.
Change to the AdminServer directory.
# cd /usr/local/bea/user_projects/domains/ProtectedResource-2/servers/AdminServer |
Create a security directory and change into it.
# mkdir security # cd security |
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 |
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 |
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.
weblogic
w3bl0g1c
Change to the ApplicationServer-2 directory.
# cd /usr/local/bea/user_projects/domains/ProtectedResource-2/ servers/ApplicationServer-2 |
Create a security directory and change into it.
# mkdir security # cd security |
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 |
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 |
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 |
Access http://ProtectedResource-2.example.com:7001/console from a web browser.
Login to the BEA WebLogic Server as the administrator.
weblogic
w3bl0g1c
Click servers.
On the Summary of Servers page, verify that both AdminServer (admin) and ApplicationServer-2 are running and OK.
Log out of the console.
Log out of the ProtectedResource–2 host machine.