Use the following as your checklist for installing Application Server 2 and the J2EE Policy Agent 2:
Download the BEA WebLogic Server installer onto Protected Resource 2.
Follow the instructions provided by BEA for obtaining and using the software.
Extract the installer files:
# /download_directory/export/weblogic/server910_solaris32.bin |
|
Enter Next. |
|
|
Enter 1. |
|
|
Press Enter to accept the default value and continue. |
|
|
Enter 2 to choose custom install. |
|
|
Enter Next. |
|
|
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-2. |
|
|
Enter 3 to modify the Listen port. |
|
|
Enter 1081. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Enter ProtectedResource-2. |
|
|
Press Enter to accept these values. |
|
|
Enter ProtectedResource-2. |
|
|
Press Enter to accept these values. |
|
|
Enter 1 to add a Unix machine. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Enter ProtectedResource-2. |
|
|
Press Enter to continue. |
|
|
Press Enter. |
Create two files necessary to automate Application Server 2 startup.
Create one file in the directory for the Application Server 2 administration server, and create one file in the Application Server 2 instance directory. The administrative user and password are stored in each file. Application Server 2 uses this information during server start-up. Without these files, Application Server 2 will fail to start. Application Server 2 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-2/servers/AdminServer # cat > boot.properties username=weblogic password=w3bl0g1c ^D # cd /usr/local/bea/user_projects/domains/ ProtectedResource-2/servers/ApplicationServer-2/ # mkdir security # cd security/ # cat > boot.properties username=weblogic password=w3bl0g1c ^D |
Start the servers.
# cd /usr/local/bea/user_projects/ domains/ProtectedResource-2/bin/ # ./startWebLogic.sh & # # 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-2/bin/ # ./startManagedWebLogic.sh ApplicationServer-2 http://ProtectedResource-2.example.com:7001 & # # ./startManagedWebLogic.sh ApplicationServer-2 http://ProtectedResource-2.example.com:7001 # cd /usr/local/bea/user_projects/domains/ ProtectedResource-1/bin/ # netstat -an | grep 7001 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 2 is up and running.
Go to the following URL:
http://ProtectedResource-2.example.com:7001/console
Log in to Application Server 2 using the following information:
weblogic
w3bl0g1c
Verify that you can successfully log into the console.
Under Domain Structure > ProtectedResource-2, expand the Environment object.
Click Servers.
On the Summary of Servers page, verify that both AdminServer(admin) and ApplicationServer-2 are running and OK.
This new account will be used by J2EE Policy Agent 2 to authenticate to the Access Manager server.
Go to Access Manage load balancer URL:
https://LoadBalancer-3.example.com:9443/amserver/UI/Login
Log in to the Access Manager console using the following information:
amadmin
4m4dmin1
On the Access Control tab, under Realms, click the realm name example.com.
Click the Subjects tab.
Click the Agents tab.
On the Agent page, click New.
On the New Agent page, provide the following information:
j2eeagent-2
j2ee4gent2
j2ee4gent2
Choose Active.
Click Create.
The new agent j2eeagent–2 is now display in the list of Agent Users.
Log out of the Access Manager console.
Create a text file, and add the Agent Profile password to the file.
The J2EE Policy Agent installer requires this file for installation.
# cd /opt/j2ee_agents/amwl9_agent # cat > agent_pwd j2ee4gent2 ^D
Application Server 2 must not be running when you install J2EE Policy Agent 2.
You must stop both the Application Server 2 instance and the administration server before installing J2EE Policy Agent 2.
# cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin/ # ./stopManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001 # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin # ./stopWebLogic.sh |
Unpack the J2EE Policy Agent bits.
cd /opt # /usr/sfw/bin/gtar -xvf /export/software/SJS_Weblogic_9_agent_2.2.tar # gunzip ../SJS_Weblogic_9_agent_2.2.tar.gz # /usr/sfw/bin/gtar -xvf ../SJS_Weblogic_9_agent_2.2.tar |
Start the J2EE Policy Agent installer.
# cd /opt/j2ee_agents/am_wl9_agent/bin # ./agentadmin --install
When prompted, provide the following information:
|
Press Enter to continue. Continue to press Enter until you reach the end of the License Agreement. |
||
|
Enter
. |
||
|
Enter ApplicationServer-2. |
||
|
Enter LoadBalancer-3.example.com. |
||
|
Enter 90. |
||
|
Enter http. |
||
|
Accept the default value. |
||
|
ProtectedResource-2.example.com |
||
|
Enter /usr/loca/bea/weblogic91. |
||
|
Enter 1081. |
||
|
Accept the default value. |
||
|
Accept the default value. |
||
|
Accept the default value. |
||
|
Enter j2eeagent-1. |
||
|
Enter
. |
||
|
Accept the default value. |
||
|
Accept the default value. |
Check the installation log to make sure there are no problems reported.