BEA Logo BEA WLCS Release 3.5

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

   http://www.oracle.com/technology/documentation/index.html   |   Search   |   PDF Files   |   Contact   |   Glossary

 

   WLCS Documentation   |   Installation Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

Supported Platforms and DDL Files

 

This chapter describes the supported hardware and software platforms for BEA Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5. Also shown are the requirements for the client graphical tool, the E-Business Control Center, that is used with all three product packages. In addition, this chapter provides summary information about Data Definition Language (DDL) files for databases certified after the initial April 2001 product release.

This chapter includes the following sections:

In this chapter, the variable BEA_HOME is used to represent a parent directory, into which BEA products and related software are installed in subdirectories. For example, the default BEA_HOME directory on a Windows system is c:\bea.

The variable WL_COMMERCE_HOME is used to represent the installation directory for the Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 product packages. For example, by default this location is c:\bea\WebLogicCommerce3.5 on Windows systems.

The variable WEBLOGIC_HOME is used to represent the WebLogic Server installation directory. By default, this location for WebLogic Server 6.0 with Service Pack 2 is c:\bea\wlserver6.0sp2.

 

Check e-docs for the Latest Platform Details

If you are reading a local or printed copy of this chapter, note that a more recent version might exist on the BEA e-docs Web site. If you have Internet access, please see http://download.oracle.com/docs/cd/E13210_01/wlcs/docs35/install/platforms.htm.

 

Important Information Regarding Platform Support

BEA certifies Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 on multiple platforms, JVMs, and operating system configurations. BEA only certifies platforms that pass rigorous internal testing. In some cases, there are problems with certain JDKs, operating systems, and hardware platforms that prevent BEA from certifying Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 in some environments.

BEA strongly recommends that you install and deploy applications using Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 only on a certified platform. BEA also suggest that you regularly check the Sun Microsystems, Inc. Web site for information and patches recommended by Sun. BEA recommends using the latest BEA certified version of the JVM that is available for your specific platform. Please note that even using a certified configuration does not guarantee that you will never encounter operating system and JVM issues while running your application. All certified platforms and the JVM have passed our internal testing.

 

Platform Details

Table 2-1 lists the supported and required software and platforms for the following:

Important: If you are reading a printed or locally installed copy of this document, note that a more recent version might exist on the BEA e-docs Web site. If you have Internet access, please see http://download.oracle.com/docs/cd/E13210_01/wlcs/docs35/install/platforms.htm and check for a more recent online version. The date of the document file's last build appears in the browser's titlebar.

Depending on your browser settings, you may need to enter Shift-Reload (Netscape) or Shift-Refresh (Microsoft Internet Explorer) to see the latest version of documentation pages you have already visited. When in doubt, please refresh your browser view to ensure that you are viewing the latest content.

Table 2-1 Supported Platforms, Environments, and Software Requirements

Requirement Type

Specification or Solution(s) Supported

Server platforms and operating systems

Client platforms and operating systems, for installations of the E-Business Control Center

Server memory and disk space

Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 require at least 128 MB of memory (RAM) to install and run. We recommend using more than this minimum requirement for your e-commerce site.

The server installation requires approximately 150 MB of temporary disk space. After the installation, the server directories require approximately 110 MB, not counting the 50 MB required by the separate E-Business Control Center directory.

Note: The E-Business Control Center is installed separately. The client can be installed either standalone, or on the same system as the server software if the platform supports both.

Client memory and disk space

BEA E-Business Control Center client requires at least 128 MB of memory (RAM) to install and run. We recommend using more than this minimum requirement.

The E-Business Control Center client installation requires approximately 75 MB of temporary disk space. After the installation, the E-Business Control Center files comprise approximately 50 MB.

Documentation memory and disk space

The installation for a local copy of the documentation files requires approximately 150 MB of temporary disk space. After the installation, the documentation files comprise about 110 MB of disk space.

Application server

If you are running WebLogic Portal 3.5 Service Pack 1 - WebLogic Server 6.0 with Service Pack 2 is required for development and production deployments. All rolling patches for WebLogic Server 6.0 are supported.

If you are running WebLogic Portal 3.5 Service Pack 2 - WebLogic Server 6.1 with Service Pack 1; or WebLogic Server 6.1 with Service Pack 2 with the patch for CR063963 is required for development and production deployments.

If you are running WebLogic Portal 3.5 Service Pack 2 with rolling patch 1 - WebLogic Server 6.1 with Service Pack 3.

If you are running WebLogic Portal 3.5 Service Pack 2 with rolling patch 2 - WebLogic Server 6.1 with Service Pack 5.

You can see which version of WebLogic Server you are using either in the command/terminal window at server startup or by looking in the weblogic.log file on the server's file system.

Note: WebLogic Portal 3.5 Service Pack 2 with rolling patch 1 and WebLogic Portal 3.5 Service Pack 2 with rolling patch 2 are supported for Win32, Solaris or HP-UX.

WebLogic Server service packs are available for download at http://support.bea.com, after you log in.

Java 2 Software Development Kit (SDK)

For all supported Microsoft Windows systems: Java 2 SDK 1.3.0 or 1.3.1.

For all supported Solaris systems: Java 2 SDK 1.3.0 or 1.3.1, and all required patches.

For all supported HP/UX systems: Java2 SDK 1.3.0 or 1.3.1.

Important: If you are installing the WLCS software on a supported, non-Solaris UNIX system, there are two steps required before and after the installation. Please see the section Special JDK Note for Non-Solaris UNIX Customers.

WebLogic Server 6.0 installs the Java 2 SDK 1.3.0. By default, the Java 2 SDK is installed in a subdirectory under the BEA_HOME directory, in:

BEA_HOME\jdk130

The installation procedure for Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 on Windows and Solaris uses its own JRE. Once installed, the product server packages are configured to use the Java 2 SDK installed by WebLogic Server. On supported UNIX systems, the Java HotSpot Server VM is used.

The E-Business Control Center for Windows and Solaris systems uses its own copy of the JRE that it installs under the BEA_HOME\E-BusinessControlCenter\jre\bin directory.

Databases and JDBC Drivers

This release has been certified for:

Note: Cloudscape 3.5.0 is certified for use with WLCS on a supported UNIX system. Cloudscape 3.5.1 is not certified for a UNIX environment.


Web browser/client

Desktop color depth and size

On Windows, a video driver that supports a minimum of 256 colors and 800x600 pixels is required for the InstallAnywhere installation procedures, the E-Business Control Center graphical user interface, and the sample JSP templates.

 

 

About the WLCS_35_DDL.zip Download File (for Service Packs 1 and 2)

Note: The WLCS_35_DDL.zip file is for use only with Service Pack 1 and 2. It has been removed from the main download site. You may get the DDL file from the BEA Support site at http://support.bea.com/welcome.jsp.

The BEA Download site includes a WLCS_35_DDL.zip file that adds support for the following types of databases:

Installing the DDL Files

Please follow these steps:

  1. Go to the WebLogic Commerce Server portion of the BEA Download site, starting at http://commerce.beasys.com/downloads/commerce_servers.jsp#wlcs. Follow the appropriate platform links to the final download page, and then download the WLCS_35_DDL.zip file.

  2. Extract the zip file, using a program such as WinZip, to the WL_COMMERCE_HOME directory. Be sure to enable the Use Folder Names option (or equivalent command).

  3. After the extraction, follow the setup and configuration steps in the appropriate readme file for your database:

    WL_COMMERCE_HOME/db/db2/7/readme.txt

    WL_COMMERCE_HOME\db\sql_server\7\readme.txt

    WL_COMMERCE_HOME/db/sybase/12/readme.txt

    These readme files include important information about the creation scripts, the SQL files, and the JDBC drivers that you will use with each database.

Installing SQL Server for Service Packs 1 and 2

If you are using SQL Server, the readme.txt file for SQL Server 7.0 (unzipped to db\sql_server\7\readme.txt) that is contained in WLCS_35_DDL.zip is missing the following instructions:

  1. Update the commerce.jdbc.pool.url property in the weblogiccommerce.properties file, which resides in the WL_COMMERCE_HOME directory.

  2. Set up the JDBC Connection Pool through the WebLogic Server Console, which will update the WL_COMMERCE_HOME\config\wlcsDomain\config.xml file.

Note: Also see the Release Notes for information about product limitations that may exist for Sybase, SQL Server, and DB2 databases.

Installing DB2 for Service Pack 1

For Service Pack 1 only, if you are using DB2, follow these additional steps before using the DB2 database with a WLCS application:

Note: For Service Pack 1 only, the WLCS_35_DDL.zip file contains readme files with detailed setup and configuration information, plus SQL files and database creation scripts. The zip file also contains a zip file named patch_CR051579.zip that DB2 customers must use.

  1. Make a backup copy of the existing ebusiness.jar file that WLCS installed in: 
    WL_COMMERCE_HOME/config/wlcsDomain/applications/wlcsApp/ebusiness.jar

  2. Go to the WL_COMMERCE_HOME directory and open the file patch_CR051579.zip.

  3. Extract the three files in the ZIP.

  4. After the extraction, follow the instructions in the README_CR051579.txt file. This patch addresses the problem in com.beasys.commerce.ebusiness.order.OrderManagerBean for the method getOrderStatus(). The ORDER_ID is a VARCHAR so the value in a SQL statement must be enclosed in quotes when using the DB2 database.

    Note: If you are using DB2 7.1 on a Linux system, applying the DB2 7.1 "Fix Pack 3" is recommended (but not required). Fix Pack 3 provides JDBC 2.0 compliance to DB2 7.1 on Linux systems.

 

Special JDK Note for Non-Solaris UNIX Customers

As discussed in Latest Kits on the Download Site, a new WLCS installer has been added to the BEA Download site for supported, non-Solaris UNIX systems. The download file name for this installer is WLCS_35_with_sp1UNIX.bin. This installer is not on the product CD that was built in April 2001.

If you are installing the kit for non-Solaris UNIX systems, there are two steps that are required before and after the installation.

  1. Before you run the WLCS_35_with_sp1UNIX.bin installation procedure, you must put the <jdk-install-directory>/bin directory in your system PATH environment variable. For example: 
    %PATH=<BEA_HOME>/jdk130/bin:$PATH
    %export PATH

    Where <BEA_HOME> is the location of the BEA Home directory on the target system.

  2. After you run the WLCS_35_with_sp1UNIX.bin installation procedure, you must edit the value of the JDK_HOME variable in the WL_COMMERCE_HOME/bin/unix/set-environment.sh file. Set JDK_HOME to the path of your JDK. For example, if the installation of WebLogic Server 6.0 with Service Pack 2 RP2 is using JDK 1.3.0, you should edit the JDK_HOME line as follows: 
    JDK_HOME=<BEA_HOME>/jdk130

    Where <BEA_HOME> is the location of the BEA Home directory.

 

About Cybercash and TAXWARE

Cybercash and TAXWARE have not been certified for IBM AIX 4.3.3 systems or Red Hat Linux 6.2 and 7.1 systems. Before you start the server on these platforms, you must remove references to the TAXWARE classes from the CLASSPATH.

In the WL_COMMERCE_HOME/bin/unix directory, edit the set-environment.sh file. For example, you could insert in set-environment.sh:

 
AIX)
 
  if [ -n "$LIBPATH" ]; then
   LIBPATH=$LIBPATH:$TAXWARE_HOME/lib:$CYBERCASH_HOME/lib:$WEBLOGIC_HOME/lib/aix
 
  else
    LIBPATH=$TAXWARE_HOME/lib:$CYBERCASH_HOME/lib:$WEBLOGIC_HOME/lib/aix
  fi
 
  export LIB_PATH
  echo "LIBPATH=$LIBPATH"
;;

If you choose to use Cybercash or TAXWARE on an AIX or Linux platform, you must complete the following steps:

  1. Acquire the product in Native form for your platform.

  2. Compile the code to your UNIX operating system.

  3. Configure the specific products.

  4. Follow our sample pipeline and configure for your specific installation.

Note, however, that an uncertified configuration on an AIX 4.3.3 system or a Linux system is not supported by BEA Systems. The Cybercash Web site is http://www.cybercash.com. The TAXWARE Web site is http://www.taxware.com.

 

back to top previous page next page

 

Copyright © 2001 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.
Contact us (documentation feedback only)