Obtain the Application Server installer from the BEA .
Start the installer.
# /download_directory/export/weblogic/server910_solaris32.bin |
Provide the following information when prompted:
|
Enter Next. |
|
|
Enter 1. |
|
|
Press Enter to accept the default value and continue. |
|
|
Enter 2. |
|
|
Press Enter to continue. |
|
|
Press Enter to accept the default value and continue. |
|
|
Press Enter to confirm the default value and continue. |
|
|
Press Enter. |
Create a new domain.
Start the BEA WebLogic Configuration Wizard.
# cd /usr/local/bea/weblogic91/common/bin # ./config.sh |
Provide the following information:
|
Press Enter to accept the default value 1. |
|
|
Press Enter to accept the default value 1. |
|
|
Press Enter to accept the default value and continue. |
|
|
Enter 2 to modify the user password. |
|
|
Enter w3bl0g1c. |
|
|
Enter 3 to confirm user password. |
|
|
Enter w3bl0g1c. |
|
|
Press Enter to accept the values and continue. |
|
|
Enter 2 to select Production Mode. |
|
|
Press Enter to accept the default value and continue. |
|
|
Enter 1 . |
|
|
Press Enter to Continue. |
|
|
Enter ApplicationServer-1. |
|
|
Enter 3 to modify the Listen port. |
|
|
Enter 1081. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Enter ProtectedResource-1. |
|
|
Press Enter to accept these values. |
|
|
Enter 1 to add a Unix machine. |
|
|
Enter ProtectedResource-2. |
|
|
Press Enter to accept these values. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Enter ProtectedResource-1. |
|
|
Press Enter to continue. |
|
|
Press Enter. |
Create two files necessary to automate Application Server 1 startup.
Create one file in the directory for the Application Server 1 administration server, and create one file in the Application Server 1 instance directory. The administrative user and password are stored in each file. Application Server 1 uses this information during server start-up. Without these files, Application Server 1 will fail to start. Application Server 1 encrypts the file, so there is no security risk even though you enter the user name and password in clear text.
# cd /usr/local/bea/user_projects/domains/ ProtectedResource-1/servers/AdminServer # mkdir security # cd security/ # cat > boot.properties username=weblogic password=w3bl0g1c ^D # cd /usr/local/bea/user_projects/domains/ ProtectedResource-1/servers/ApplicationServer-1/ # mkdir security # cd security/ # cat > boot.properties username=weblogic password=w3bl0g1c ^D |
Start the servers.
# cd /usr/local/bea/user_projects/domains/ ProtectedResource-1/bin/ # nohup ./startWebLogic.sh & #tail -f nohup.out ... # netstat -an | grep 7001 xxx.xx.72.151.7001 *.* 0 0 49152 0 LISTEN 127.0.0.1.7001 *.* 0 0 49152 0 LISTEN # # cd /usr/local/bea/user_projects/domains/ProtectedResource-1/bin/ # nohup ./startManagedWebLogic.sh ApplicationServer-1 http://ProtectedResource-1.example.com:7001 & # cd /usr/local/bea/user_projects/domains/ ProtectedResource-1/bin/ # netstat -an | grep 1081 xxx.xx.72.151.1081 *.* 0 0 49152 0 LISTEN 127.0.0.1.1081 *.* 0 0 49152 0 LISTEN xxx.xx.72.151.33425 xxx.xx.72.151.1081 49152 0 49152 0 ESTABLISHED xxx.xx.72.151.1081 xxx.xx.72.151.33425 49152 0 49152 0 ESTABLISHED |
Verify that Application Server 1 is up and running.
Go to the following URL:
http://ProtectedResource-1.example.com:7001/console
Log in to the Application Server 1 console using the following information:
weblogic
w3bl0g1c
Verify that you can successfully log into the console.
Under Domain Structure , expand the Environment object
Click Servers.
On the Summary of Servers page, verify that both AdminServer(admin) and ApplicationServer-1 are running and OK.