How to Install BEA WebLogic Server™
on OpenVMS™ Alpha™

Set up your a disk, directory, and account as follows before installing WebLogic:

1. Log in to the SYSTEM account or another privileged account.

2. Create an account called weblogic510 and set its default device and directory to disk$weblogic:[weblogic510], which you will create in the following steps.
   

   The weblogic510 account should have the following minimum quotas: /PGFLQUO=400000/WSEXTENT=64000/WSQUO=16384/FILLM=1024
   

3. Create or convert an ODS-5 disk and define a system logical called disk$weblogic pointing to this disk. For example:

   $ set volume/structure_level=5 disk_name:
   $ Define disk$weblogic disk_name:

4. Create a directory on the ODS-5 disk called disk$weblogic:[weblogic510] and set the owner to the weblogic510 account. For example:

   $ create/dir/own=weblogic510/ver=0 disk$weblogic:[weblogic510]

5. Create the WLS_ROOT logical:

   $ define/system/exec/trans=conceal wls_root disk$weblogic:[weblogic510.]

   Add this command to SYS$STARTUP:SYSTARTUP_VMS.COM

   Usage Notes for WebLogic Logicals

   If you wish to have several installations of WebLogic Server on your system, you should not define WLS_ROOT systemwide and its definition should not be placed in SYS$STARTUP:SYSTARTUP_VMS.COM. Instead, you should define WLS_ROOT as a jobwide logical name and place its definition in the LOGIN.COM file of the weblogic510 account.

   If your SYSTARTUP_VMS.COM command procedure doesn't already contain a command to mount the disk$weblogic device, you need to add a command to mount the device. Do not mount the disk using weblogic as the logical name - this will cause problems when you use the JAR commands. Choose an alternative logical name for the device, such as disk$weblogic.

6. Log in under weblogic510 and execute the following commands:

$ jar xf weblogic510SP[n].zip

Additional steps to run Cloudscape database

1. Use FTP to copy the Cloudscape Updater file (cloudscape350_WLS_51.zip) to the wls_root:[weblogic] directory.
   
   
2. Move any existing files ( [.eval.cloudscape.data]*.*) and Cloudscape archives ([.eval.lib.cloudscape]*.jar) to a safe location on your disk.
   
   
3. Use JAR to unpack the Cloudscape Updater:
   
   $ jar xf cloudscape350_WLS_51.zip

5. Create the following directory, which are used by WebLogic Server to store translated and compiled JSP pages and other generated files:

   wls_root:[weblogic.myserver.classfiles]

6. Copy the WebLogicLicense.xml file you received from BEA to wls_root:[weblogic.license]
   
   
7. Set default to: disk$weblogic:[weblogic510]
   
   
8. Copy openvms_wls.jar to DISK$WEBLOGIC:[WEBLOGIC510] and use the JAR command to unpack the contents:

   $ jar xf openvms_wls.jar

Check the Service Pack version
The OpenVMS-specific command files (supplied in openvms_wls.jar) setEnv.com and startWebLogic.com both contain references to the Service Pack 8 jar files. If you install a later service pack than Service Pack 8, you will need to edit these files to fix the references to these jar files. Search the files for sp8 and replace all occurrences with the correct string.

Additional step to run the Cloudscape database
In [.weblogic]setenv.com, locate the OpenVMS Java Settings section, and select java_version = "130" (by uncommenting this line and commenting the previous line for "122").

Starting WebLogic Server and Console

Start the server and open the WebLogic Console as follows:

1. Execute:

   $ @login.com
   

2. Start WebLogic Server using:

   $ @startweblogic

3. Log into another window and start the WebLogic Console using:

   $ @startconsole

   When the console comes up on your workstation, select Attach to a WebLogic Server or Cluster from the File menu. The password is: weblogic

   Starting the console from Windows
   To start the console remotely from a Windows system do the following:

   $ define decw$display wsa1:
   $ Set Display/Transport=TCPIP/Node=16.32.128.33 !use your IP address here
   $ java - mx32m weblogic.Console"