To Modify the Application Server Startup File

1. Go to the following Protected Resource 1 directory.

   The J2EE Policy Agent installer creates a new file in the Application Server bin directory:

   # cd /usr/local/bea/user_projects/domains/ProtectedResource-1/bin

2. Make a backup of the file setDomainEnv.sh.

3. In the setDomainEnv.sh file, at the end of the file append the following:

   echo "Setting Policy Agent Env..." . /usr/local/bea/user_projects/domains/ProtectedResource-1/bin/ setAgentEnv_ApplicationServer-1.sh

   This command references the file the installer created in the Application Server bin directory.

4. Save the setDomainEnv.sh file.

5. Change permissions for the setAgentEnv_ApplicationServer-1.sh file:

   # cdmod 755 setAgentEnv_ApplicationServer-1.sh

6. Stop Application Server 1.

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

7. Stop the administration server.

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

8. Start the administration server.

   # nohup ./startWebLogic.sh &
   # tail -f nohup.out

   Watch for startup errors.

9. Start Application Server 1.

   # nohup ./startManageWebLogic sh ApplicatoinServer-1 
   http://ProtectedResource-1.example.com:7001 &
   tail -f nohup.out

10. Run the netstat command to verify that Application Server 1 is up and listening.

    # netstat -an | grep 1081
    xxx.xx.72.151.1081		*.*		0		0	49152		0	LISTEN
    127.0.0.01.1081			*.*		0		0	49152		0	LISTEN