Supported Configurations for WebLogic Server 5.1
 |
 |
 |
|
 |
Get Adobe Reader |
This document contains installation instructions for the following platforms:
For general information about Java technology for Compaq Alpha Systems, see the Compaq Java Technology Center website.
OpenVMS v7.2 has been tested on WebLogic Server 5.1.with jdbcKona/MSSQLServer4. Note the following, however:
ActivatableRuntimeDescriptor.getStub() is not supported on this platform.
There are a number of known issues associated with this release on this platform:
TMJOIN and TMRESUME in javax.transaction.xa.XAResource. The AS/400 XA JDBC driver doesn't work with WebLogic Server's JTA transaction manager. abcd1234. You should change it the first time when server is started. For information on how to download this platform, see Download WebLogic Server for Your Platform.
===> CRTSAVF FILE (QGPL/WEBL610sp2)
This command creates a save file on the AS/400 where you will transfer the webl610sp2 file.
===> DLTF FILE(QGPL/WEBL610sp2)
On your Windows NT workstation, you can also delete the .zip file you downloaded and the webl610sp2 file.
WEBLOGIC61/INSWEBL programs (*PGM) and command (*CMD) are shipped with public authority set to *USE. Once the install has been run successfully, the administrator may set the authority on these objects to PUBLIC *EXCLUDE. Your AS/400 now has a WebLogic IFS directory containing the WebLogic Java classes as well as configuration files and example programs.
The Java classes are transformed with the AS/400 Java transformer with level 40 optimization, so AS/400 direct executables for WebLogic are used.
/weblogic/610sp2. The BEA home directory is /weblogic/61sp2. The WebLogic product installation directory is /weblogic/61sp2/wlserver6.1.For more information about the BEA home directory, please refer to the discussion here:
http://download.oracle.com/docs/cd/E13222_01/wls/docs61/install/instpre.html#1066128
WebLogic administrative users have *ALL authority for the commands in the WEBLOGIC61 library and *RWX authority on certain files in the /weblogic directory. To allow a user to start and stop the server or to modify any of these files, you can add GRPPRF(WLADMIN) to their profiles.
To create a new user with authority to administer WebLogic, use this command:
The WEBLOGIC61/INSWEBL command creates the WEBLOGIC user profile with authorizations of *NONE. You cannot log in as WEBLOGIC. However, you can add users to the WLADMIN group, allowing them to start WebLogic Server.
This installer can not generate evaluation license dynamically. Please contact BEA customer support to download an evaluation license at the BEA product download site.
Before you start WebLogic Server, you must add the WebLogic classes to the CLASSPATH environment variable.
The CLASSPATH environment variable for the session in which you run WebLogic Server must contain these classes:
You must also set the QIBM_MULTI_THREADED environment variable to Y before you run STRWEBL, JAVA, or RUNJAVA commands or the JAVA command in an interactive QSHELL shell.
You can enter the CLASSPATH as a parameter when you run the STRWEBL CL command. Or you can use ADDENVVAR to add variables to your environment, CHGENVVAR to change an environment variable, or WRKENVVAR to add or modify variables in the environment.
The next sections describe how to set the CLASSPATH and other variables on the AS/400 using ADDENVVAR or QSHELL and on a Windows NT workstation. (The commands are displayed on several lines here for clarity, but they should be typed without line breaks when you enter them.)
The following commands set the CLASSPATH and QIBM_MULTI_THREADED environment variables in an AS/400 session:
If you set environment variables in your session before you start QSHELL, the variables remain set in QSHELL, unless a ".profile" file in your home directory or the /etc/profile file resets environment variables.
You can set environment variables for every interactive QSHELL shell you start with STRQSH or QSH by setting the CLASSPATH in the .profile file in your home directory. An administrator can set environment variables globally by adding them to the /etc/profile file, which is executed whenever any user starts a QSHELL shell with the STRQSH or QSH commands.
To set environment variables in QSHELL, use these commands at the prompt, or add them to one of the profile files:
You must set the CLASSPATH environment variable on a workstation running WebLogic classes from the AS/400. The QIBM_MULTI_THREADED environment variable is needed only when you are running Java classes in the AS/400 VM.
In this example, AS400SRVR is the name of the AS/400 server where WebLogic Server is installed.
The WEBLOGIC61/STRWEBL command starts WebLogic Server. This command changes to the WEBLOGIC account before it starts the server. This is important because objects the server creates belong to the WEBLOGIC account. If you start the server using a method other than the WEBLOGIC/STRWEBL command, you may experience problems with permissions. With QSHELL you can start WebLogic sever using the shell script shipped with WebLogic server, but WebLogic Server will be using your user profile. This could be a security problem in a production environment.
To start WebLogic Server with the WEBLOGIC61/STRWEBL command:
"/weblogic/610sp2/wlserver6.1".QSHELL session within the current job. You should press F3 to quit a QSHELL session, otherwise WebLogic Server won't start. mydomain (the default shipped with Weblogic)myserver (the default shipped with WebLogic). *ROOT_INSTALL_DIR as default, which will point to /weblogic/610sp2 *CURDIR (which will point to /weblogic/610sp2/ wlserver6.1).For more information about WebLogic Server startup properties, see Starting and Stopping WebLogic Servers.
For parameters such as CLASSPATH, there may not initially be enough room to enter the entire value. You can expand a line by entering an ampersand (&) before you enter the value. Keep entering ampersands until there is enough room to enter your value. Press Enter to execute the command.
For example, the following command starts the default server shipped with WebLogic Server:
===> WEBLOGIC61/STRWEBL DOMAINNAME(mydomain) SERVERNAME(myserver) PROPERTIES((java.security.policy '=/weblogic/610sp2/wlserver6.1/lib/weblogic.policy'))
If you start the WebLogic Server interactively (Submit set to *NO), do not press F3 or F12 to exit the Java Command Entry Screen until you see a message similar to this:
See the WebLogic Server Administration Guide for detailed instructions on administering WebLogic, including setting up WebLogic Server as an HTTP server.
WebLogic Server has extensive properties to give you a fine degree of control its operation.
Also read about the property-related changes in the release notes for WebLogic Server.
You can shut down WebLogic Server through the Administration Console, or enter the ENDWEBL command:
Enter the WebLogic administrative user name (usually system) and password, and then press Enter to continue. Wait until you see a message similar to the following:
After this message appears, you can press F3 to exit the Java Command Entry Screen and return to the AS/400 Command Entry screen.
BEA ships three default servers with WebLogic product. The configuration repository can be found at /weblogic/610sp2/wlserver6.1/config.
Server myserver in Domain mydomain is the default product server.
The initial system password of WebLogic Servers is abcd1234. You should change it the first time when server is started.
Two additional demo domains are also shipped: PetStore and Examples.
These servers were supposed to use the evaluation copy of CloudScape database shipped with WebLogic. We found Cloudscape doesn't work with JDK1.3.1 on AS/400, so a DDL for demo database is shipped with WebLogic.
To set up the demo database, execute the following CL command:
A demo database named WLSDEMO will be created on your machine. If you want to use a different name for the database, please edit member WLSDEMO in the file WEBLOGIC61/SQLSRC, replacing the string wlsdemo with the name you chose.
To set up proper JDBC connection pool properties like user name and password, you also need to modify file config.xml in these directories:
For more information about setting up JDBC connections please refer to the WebLogic for IBM AS/400e Technical FAQ.
/weblogic/610sp2/wlserver6.1/config/petstore/config.xml, seting user id and password for the JDBC connection pool to demo database WLSDEMO. The AS/400 Developer Center is your starting point for using WebLogic Server on the IBM AS/400. From the Developer Center you can access documentation written specifically about using WebLogic software in an AS/400 environment, as well as documents relevant to all WebLogic users.
For more supported platform information, see IBM S/390 with OS/390.
For general information about S/390, OS/390, and USS/390, see IBM's S/390 website.
Install WebLogic Server on OS/390 using the WebLogic .zip archive distribution. Follow the instructions for installing from a .zip archive for your version of WebLogic Server.
You can download the latest JDK that runs on WebLogic Server 5.1 from the S/390 Java page at:
After you install WebLogic Server on OS/390, you must run the USS390PostInst utility, which is in the util390.jar file, to convert text files from ASCII to EBCDIC encoding. It is only necessary to do this one time after you install. Follow these steps:
|
|
|