Corporate Info | News | Solutions | Products | Partners | Services | Events | Download | How To Buy

# How to Install BEA WebLogic Server™ on OpenVMS™ Alpha™ Download BEA WebLogic Server System Requirements Installation Procedure Setting up a disk, directory, and account to run WebLogic Installing the WebLogic kit and service pack Starting WebLogic Server and Console
BEA WebLogic Server 5.1.0 Is Not an OpenVMS-Only Kit Be aware of some limitations in the currently avalailable WebLogic Server kit for OpenVMS users: The install process installs many non-OpenVMS files. (You get files for Windows NT, IBM AIX, Sun Solaris, and so on.) The configuration files are not tailored for the Compaq Java environment. A supplemental OpenVMS kit is provided with OpenVMS-specific configuration and startup command procedures.
## Download BEA WebLogic Server In order to test an EJB middle component on OpenVMS Alpha, you will require an EJB application server. You may download the WebLogic Application Server for a 30-day evaluation from the BEA WebLogic Server Downloads page. Required BEA WebLogic Server Files WebLogic Server 5.1.0 Select For non-Win32 Users Latest Service Pack Both kits available from http://commerce.bea.com/downloads/weblogic_server.jsp Additional download to run Cloudscape database If you want to use the WebLogic demonstration database, also download Cloudscape Version Updater for WebLogic Server 5.1.0. ## System Requirements Hardware A nonsystem disk that can be converted or initialized to ODS-5. Note The disk must not have page or swap files on it. Software OpenVMS 7.2-1 or later Java 2 SDK 1.2.2-3 Available from Java for Alpha Systems Download Page: http://www.compaq.com/java/download/index.html Requirement to run Cloudscape database If you want to use the Cloudscape demonstration database that comes with WebLogic Server, you will need to install the Java 2 SDK 1.3.0-1. Java Software Patches (ECOs) necessary for Java 2 SDK 1.2.3-3. Available from Java Patch Installation Page: http://www.compaq.com/java/download/jdk_ovms/vms122patches.html Supplemental Software OpenVMS supplemental files (openvms_wls.jar) is available with these instructions and contains customized command and settings files for OpenVMS: startWebLogic.com, setEnv.com, weblogic properties, startSNMPAgent.com, startConsole.com, vms_javac.com, login.com, weblogic.policy, _java.policy ## Installing WebLogic Server on OpenVMS Alpha Review all instructions before proceeding. An ODS-5 disk is required. ### Setting up a disk, directory, and account to run WebLogic Set up your a disk, directory, and account as follows before installing WebLogic: Log in to the SYSTEM account or another privileged account. 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 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: 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] 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. Log in under weblogic510 and execute the following commands:

> $ @sys$common:[java$122.com]java$122_setup.com !if you're using JAVA V1.2.2

> $ @sys$common:[java$130.com]java$130_setup.com !if you're using JAVA V1.3.0

> $ set process/parse_style =extended !long filenames and case sensitivity

> $ define/nolog java$filename_controls "553648127" !allow filenames > 39.39 bytes

> $ define/nolog/job decc$argv_parse_style enable !preserve argv case from DCL

> $ define/nolog/job decc$efs_case_preserve enable !enable ODS-5 names when you 'unjar' the kit

### Installing the WebLogic kit and service pack Install the main kit and service pack as follows: Use FTP to copy the main installation file, weblogic510.zip, to the disk$weblogic:[weblogic510] disk. Install the WebLogic kit by setting default to disk$weblogic:[weblogic510] and using the JAR command to unpack the archive: $ jar xf weblogic510.zip This assumes that the .zip file resides in the weblogic510 directory. Note Depending on the speed of the machine, this could run for over 20 minutes. It should create the WLS directory structure starting with the WebLogic directory under [weblogic510] - that is, [weblogic510.weblogic]. Use FTP to copy the latest service pack file, weblogic510SP[n].zip, to the wls_root:[weblogic] directory. Install the service pack by setting default to wls_root:[weblogic] and using the JAR command to unpack the archive: $ jar xf weblogic510SP[n].zip Additional steps to run Cloudscape database Use FTP to copy the Cloudscape Updater file (cloudscape350_WLS_51.zip) to the wls_root:[weblogic] directory. Move any existing files ( [.eval.cloudscape.data]*.*) and Cloudscape archives ([.eval.lib.cloudscape]*.jar) to a safe location on your disk. Use JAR to unpack the Cloudscape Updater: $ jar xf cloudscape350_WLS_51.zip 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] Copy the WebLogicLicense.xml file you received from BEA to wls_root:[weblogic.license] Set default to: disk$weblogic:[weblogic510] 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: Execute: $ @login.com Start WebLogic Server using: $ @startweblogic This should lead to a lengthy list of messages, the last one containing the message: WebLogic Server started. The server deploys a number of sample EJBs that come with WLS. To run the stateless session sample client log into another window and execute: $ java examples.ejb.basic.statelessSession.Client Output from this command looks similar to: Beginning statelessSession.Client... Creating a trader Buying 100 shares of BEAS. Buying 200 shares of MSFT. Buying 300 shares of AMZN. Buying 400 shares of HWP. Selling 100 shares of BEAS. Selling 200 shares of MSFT. Selling 300 shares of AMZN. Selling 400 shares of HWP. Removing the trader End statelessSession.Client... 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"

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.