Supported Configurations for WebLogic Server 6.1
 |
 |
 |
|
 |
Get Adobe Reader |
Note: WebLogic Server 6.1 was retired November 14, 2006. See Supported Configurations.
This document contains installation instructions for the following platforms:
Use the following steps to download and install WebLogic Server 6.1 SP6:
weblogic610sp5_aix.bin file and CR104985_610sp5_aix.jar file from http://commerce.bea.com/support/supportversions.jsp?file=/products/weblogicserver/support/support.html.http://download.oracle.com/docs/cd/E13222_01/wls/docs61/install/instprg.html#1040228
http://download.oracle.com/docs/cd/E13222_01/wls/docs61/install/instcon.html#1008419
Use the following steps to download and install WebLogic Server 6.1 SP4:
For Console-Mode, see http://download.oracle.com/docs/cd/E13222_01/wls/docs61/install/instcon.html
For general information about Java technology for HP (formerly Compaq) Alpha Systems, see the hp OpenVMSTM systems website.
A HP Alpha processor with a non-system disk that can be converted or initialized to ODS-5.
Note: The disk must not have page or swap files on it.
wls61sp3_OpenVMS_supp.jar) are available from BEA with your WebLogic for OpenVMS download and contain customized command and settings files for OpenVMS. These files will be automatically copied to the proper directories in a later step: Review all instructions before proceeding. An ODS-5 disk is required.
Set up your ODS-5 disk, directory, and account as follows before installing WebLogic Server:
weblogic610 and set its default device and directory to wldisk:[weblogic610], which you will create in the following steps. The weblogic610 account should have the following minimum quotas:
/PGFLQUO=1500000/WSDEF=8000/WSEXTENT=32000/WSQUO=16000/BYTLM=300000/FILLM=1024
wldisk pointing to this disk. For example: $ initialize/structure_level=5 DKA100: wldisk
$ define/system/exec wldisk DKA100:
Note: also include this command in sys$startup:systartup_vms.com
wldisk:[weblogic610] and set the owner to the weblogic610 account. For example: wldisk:[kits] and set the owner to the weblogic610 account. For example: $ set default wldisk:[weblogic610]
$ @sys$common:[java$131.com]java$131_setup.com fast
$ 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
For information on how to download this platform, see Distribution and Installation Information.
From the SYSTEM account, install the WebLogic Server kit as follows:
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 [weblogic610]— that is, [weblogic610.wlserver6_1].
An example of the install script is as follows:
Choose Locale...
----------------
Deutsch
->1- English
Espanol
Francais
Introduction text, and the BEA WebLogic License is displayed at this point
DO YOU AGREE WITH THE TERMS OF THE LICENSE? (Y/N): Y
Choose Install Set
------------------
Please Choose the Install Set to be installed by this installer.
->1- Server and Examples
2- Server Only
3- Customize...
ENTER THE NUMBER FOR THE INSTALL SET, OR TO ACCEPT THE DEFAULT
: 1
Choose BEA Home Directory
-------------------------
1- Create a New BEA Home
Enter a number: 1
Specify a New BEA Home: /wldisk/weblogic610
==================================================
Choose Product Directory (! NOTE: avoid "." in VMS directory names !)
------------------------
1- Modify Current Selection (/wldisk/weblogic610/wlserver6.1)
2- Use Current Selection (/wldisk/weblogic610/wlserver6.1)
>Enter a number: 1
Specify Product Installation Directory: /wldisk/weblogic610/wlserver6_1
1- Modify Current Selection (/wldisk/weblogic610/wlserver6_1)
2- Use Current Selection (/wldisk/weblogic610/wlserver6_1)
Enter a number: 2
IMPORTANT: The command procedures supplied by OpenVMS assume this exact directory structure. If you choose a different directory name, you will need to modify the supplied command files.
==================================================
Default Server Configuration
----------------------------
1- Modify WebLogic Admin Domain Name (mydomain)
2- Modify Server Name (myserver)
3- Modify Listen Port (7001)
4- Modify Secure (SSL) Listen Port (7002)
5- Done Configuration
Enter a number: 5
==================================================
Create System Password
----------------------
Password: password_of_your_choice
Good Password! Installing now....
==================================================
Installing...
-------------
Install Complete
----------------
Congratulations. 'WebLogic Server' has been successfully installed to:
/wldisk/weblogic610/wlserver6_1
PRESS TO EXIT THE INSTALLER:
$
Copy the new license you obtained from BEA to wldisk:[weblogic610.wlserver6_1.license]. Set default to wldisk:[weblogic610], and use the JAVA command to run LicenseMerger, which installs the new WebLogic Server license. For example:
$ copy *new_license_filename* to wldisk:[weblogic610.wlserver6_1.license]
$ set default wldisk:[weblogic610]
$ java -cp [.utils]utils.jar com.bea.installer.registry.LicenseMerger -
_$ license.bea wldisk:[weblogic610.wlserver6_1.license]*new_license_filename*
Note: WebLogic Server V6.1 automatically creates a new updated config.xml on startup, based on your current config.xml and dynamic environment. If you wish to preserve your config.xml, you are recommended to make a copy of this file (for example, config.xml_backup) and copy it to config.xml prior to starting the server. There is no current method of turning off this feature in WebLogic Server V6.1.
$ set def wldisk:[weblogic610.wlserver6_1.config.mydomain]
$ @startWebLogic
WebLogic Server Password: *enter the password you supplied during installation*
This should take few minutes and lead to messages: WebLogic Server started and ListenThread listening on port 7001. At this point, you are ready to run your application with BEA WebLogic Server.
$ set def wldisk:[weblogic610.wlserver6_1.config.petstore]
$ @startPetStore
WebLogic Server Password: *enter the password you supplied during installation*
Then, using Internet Explorer, access the PetStore application via:
Note: Running the PetStore example could be a good way to verify that your installation is complete.
You may use the supplied ShutdownWebLogic.com command file to shut down the WebLogic Server as follows:
$ @wldisk:[weblogic610]shutdownWebLogic.com
With this command file, you may supply either interactively or as parameters:
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 Distribution and Installation Information.
===> 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.
**********************************************
BEA WEBLOGIC SERVER 6.1 SP2 README.TXT FILE
**********************************************
Copyright (c) 2002 BEA Systems Inc. All Rights Reserved.
This README file contains information about the OS/390 release and contains installation instructions.
This file and the installation shell scripts are in EBCDIC (Cp1047). All other text files in this distribution are in ASCII (ISO-8859-1). To facilitate the operation in this mode there are shell scripts and executable binaries in the $WL_HOME/bin/os390 directory. These programs are:
avi = ASCII vi - converts file to EBCDIC, edits and convert back to ASCII.
acnv = ASCII convert - converts file to EBCDIC.
a2e = ASCII to EBCDIC filter - converts stdin from ASCII to stdout in EBCDIC.
e2a = EBCDIC to ASCII filter - converts stdin from EBCDIC to stdout in ASCII.
javac = Java Compile - Compiles in ISO-8859-1 encoding.
javacmd = Java execute script - Runs Java with the ISO-8859-1 encoding.
repjdk = Replicate JDK - Replicates the JDK and makes changes for ASCII (ISO-8859-1) operation.
Installation:
1. Download the WebLogic generic distribution, be sure to specify binary mode transfers.
2. Download the Weblogic uss_support zip file, in binary mode.
3. Download the install.sh and installer.properties, in text mode.
4. Edit the installer.properties for your installation and run the install shell script.
$ sh install.sh weblogic_generic.zip installer.properties
This will install the generic WebLogic on your system. The
output of the installation is written into the file
install.log in ASCII.
5. Export the WL_HOME variable to point to the WebLogic installation.
$ export WL_HOME=/YOUR_INSTALLATION_DIRECTORY/wlserver6.1
6. Overlay the installation with the uss_support modules:
$ cd $WL_HOME
$ jar xf YOUR_DIST_DIRECTORY/uss_support.zip
$ chmod +x $WL_HOME/bin/os390
7. Add weblogic/bin to your execution path.
$ export PATH=$WL_HOME/bin:$WL_HOME/bin/os390:$PATH
8. Replicate the JDK for WebLogic execution. This is necessary as java compiler must be run in the correct mode. For the example, we assume that the JDK is in the /pub directory. Also, you MUST be in super user mode to perform this step (ie. login to OPEN1).
$ cd /pub
$ repjdk J1.3 WLSJ1.3
This step will copy the current JDK, J1.3, into a new
directory, WLSJ1.3. All WebLogic operation MUST run against
this copy of the JDK. If the new directory exists, it will be
overwritten.
9. Copy the java.login file to your $HOME directory. This allows the JAAS to run the WebLogic supplied security methods and not the ones from IBM.
$ cp $WL_HOME/java.login $HOME/.java.login.config
10. The config.xml files for your applications, for example PetStore, must be edited to use the JDK that was replicated in step 8. For example:
$ cd $WL_HOME/config/petstore
$ avi config.xml ! Remember it's in ASCII !
11. Convert execution shell scripts to EBCDIC prior to use. For example:
$ acnv startPetStore.sh
If you have a replicated JDK, step 8, you'll need to change
the JAVA_HOME to reflect its location.
12. Create a password file, password.ini, in ASCII for WebLogic to start. For example:
$ avi password.ini
Operation:
The operation of the WebLogic Server is like the operation on any other Unix style platform. Except, that you have the ASCII files on an EBCDIC platform.
All log files and text files (html, xml, etc.) are in ASCII and must be viewed or edited with the utilities mentioned above. Should you encounter a shell script file in ASCII, it will appear as garbage on your screen, you can convert it using the acnv program. For example:
$ acnv shell.sh
install.sh shell script and the installer.properties file (See OS390_README.TXT for details). The uss_support.zip file is used to overlay the installation with OS/390 specific binaries and the OS390_Petstore.zip contains the files to allow PetStore to use DB2.
For general information about SuSE Linux for S/390, see IBM's Linux for s/390 website:
Install WebLogic Server on SuSE Linux for S/390 using the WebLogic .zip archive distribution. Follow the instructions for installing from a zip archive for your version of WebLogic Server.
This documentation contains information about the Linux/390 release and contains installation specific instructions for WebLogic 6.1 users.
This version is installed and operates just like any other Unix version of WebLogic.
After installation, you must create a file in your login home directory called .java.login.config with the contents:
This file allows the JAAS security to invoke the WebLogic Server security module rather than the one from IBM.
s390.jar file in the CLASSPATH. With the SR1 release of the JDK, IBM changed the way IIOP works. To include the .jar file, put: Download the db2petstore.zip file from:
If you wish to configure the PetStore application to use DB2, then follow these steps:
db2petstore.sql and change the CONNECT statement to match your DB2 configuration and accounts. db2petstore.sql to install the database schema objects and insert the sample data into the database. startPetStore.sh to add $DB2_HOME/sqllib/java12/db2java.zip in the CLASSPATH to replace the Cloudscape definitions. Also, you can remove the -Dcloudscape properties from the WebLogic startup command line. Set the DB2_HOME environment variable to the DB2 installation directory. For example: setExamplesEnv.sh from WLS_HOME/config/examples. WLS_HOME is the location of the WebLogic installation directory. <env-entry-name>ejb/order/OrderDAOClass</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
com.sun.j2ee.blueprints.customer.order.dao.OrderDAOCS
<env-entry-name>ejb/order/OrderDAOClass</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
com.sun.j2ee.blueprints.customer.order.dao.OrderDAODB2
This documentation contains information about the Linux/390 release and contains specific information for WebLogic 6.1 Service Pack 2 users.
The JDK on the 2.4 kernel requires the 20020415 version of glibc and two updates to the kernel:
For general information about Red Had Linux for S/390, see IBM's Linux for s/390 website:
Install WebLogic Server on Red Hat Linux for S/390 using the WebLogic .zip archive distribution. Follow the instructions for installing from a zip archive for your version of WebLogic Server.
This documentation contains information about the Linux/390 release and contains installation specific instructions for WebLogic 6.1 users.
This version is installed and operates just like any other Unix version of WebLogic.
After installation, you must create a file in your login home directory called .java.login.config with the contents:
This file allows the JAAS security to invoke the WebLogic Server security module rather than the one from IBM.
s390.jar file in the CLASSPATH. With the SR1 release of the JDK, IBM changed the way IIOP works. To include the .jar file, put: Download the db2petstore.zip file from:
If you wish to configure the PetStore application to use DB2, then follow these steps:
db2petstore.sql and change the CONNECT statement to match your DB2 configuration and accounts. db2petstore.sql to install the database schema objects and insert the sample data into the database. startPetStore.sh to add $DB2_HOME/sqllib/java12/db2java.zip in the CLASSPATH to replace the Cloudscape definitions. Also, you can remove the -Dcloudscape properties from the WebLogic startup command line. Set the DB2_HOME environment variable to the DB2 installation directory. For example: setExamplesEnv.sh from WLS_HOME/config/examples. WLS_HOME is the location of the WebLogic installation directory. <env-entry-name>ejb/order/OrderDAOClass</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
com.sun.j2ee.blueprints.customer.order.dao.OrderDAOCS
<env-entry-name>ejb/order/OrderDAOClass</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
com.sun.j2ee.blueprints.customer.order.dao.OrderDAODB2
|
|
|