Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary   |   What's New
WLCS Doc Home   |   Installing Commerce Servers   |   Previous Topic   |   Next Topic   |   Contents

Installing BEA WebLogic Commerce Servers includes the following topics:

Licensing WebLogic Commerce Servers

How WebLogic Commerce Servers licensing works

How to reinstall the WebLogicCommerceLicense.xml file by hand

Installation Instructions on Windows NT

Installation Instructions on UNIX

Installation Notes

Where to Go Next

When you register to download WebLogic Commerce Servers (WLCS), you should also download a current evaluation license. If you received the product on a disk, you will receive a license file via e-mail to the e-mail account specified on the purchase order.

Note: If you need a new evaluation license, revisit commerce.beasys.com, go through the download process, and download only the evaluation license.

WebLogic Commerce Servers license keys are stored in WL_COMMERCE_HOME/license in a file called WebLogicCommerceLicense.xml. This file must reside either in your working directory or in a directory included in your WEBLOGIC_CLASSPATH.

Note: WLCS ships with the license file in the CLASSPATH. If you have problems starting the server, we recommend you check the WL_COMMERCE_HOME\license directory and add the directory to your WEBLOGIC_CLASSPATH if necessary. Moving the WebLogicCommerceLicense.xml file to a directory that is already in your CLASSPATH will also work.

If you receive a new WebLogicCommerceLicense.xml and need to reinstall it, you should:

1. Delete any old versions of WebLogicCommerceLicense.xml from your WEBLOGIC_CLASSPATH.

2. Verify that the WebLogicCommerceLicense.xml file is in your CLASSPATH or working directory. The easiest approach is to keep your WebLogicCommerceLicense.xml in the WL_COMMERCE_HOME/license directory and ensure this directory is in your WEBLOGIC_CLASSPATH.

   Note: If you have two license statements for the same product in the file, only the first one will be used.

1. Start the installation by opening the installation package, WLCS_201_NT4.exe.

2. Click through the Welcome and Software License Agreement screens.

3. In the Select your WebLogicCommerceLicense.xml screen, point the wizard to the WebLogic Commerce Server license (WebLogicCommerceLicense.xml) on your server. Click Next after you locate the license file.

   

4. The InstallShield autodetects your JDK, WebLogic Server, and Rational Rose installations. If it doesn't find one of those items, it asks you to point to the directory that contains it.

   Note: Rational Rose is required for certain features in the Components, but it's not required to run the system. Refer to the Components documentation for information about using Rational Rose with the Components.

5. In the Select Destination Directory screen, point to the installation directory you want to use. The default installation directory is \weblogicCommerce. Click Next.

6. After the installation completes, the BEA WebLogic Commerce Server has been successfully installed screen appears.

   

7. Run StartCommerce.bat to start the Cloudscape version of WebLogic Commerce Servers 2.0.1.

   Note: See Setting Up an Oracle Database to run WebLogic Commerce Servers with a database other than the Cloudscape database that ships with the system.

1. Unjar the WLCS_201_UNIX.zip installation file in a directory. This process creates a directory called /WebLogicCommerce.

2. Change to the /WebLogicCommerce directory and run install.sh to create the startup files for WebLogic Commerce Servers. You need to know the location of the JDK and WebLogic Server to complete the installation.

3. Make a license directory at <install-dir>/license.

4. Copy your WebLogicCommerceLicense.xml file to the new <install-dir>/license directory.

5. Run StartCommerce.sh to start the Cloudscape version of WebLogic Commerce Servers 2.0.1.

   Note: You may need to change file permissions to run the script.

WLCS 2.0.1 ships with two supported database configurations: Oracle and Cloudscape. To enable easier deployment of WLCS with these databases, BEA provides configuration files for each database configuration. The *-cmp files specify Cloudscape configuration and *-bmp files specify Oracle configuration. You may need to copy these files into the default weblogic.properties and weblogiccommerce.properties files, depending on your database. Refer to Configuring Properties Files for more information about configuring the files.

1. Change to the installation directory and start WLCS by running StartCommerce.bat (StartCommerce.sh for UNIX). The default installation path is \weblogicCommerce\StartCommerce.bat or /weblogicCommerce/StartCommerce.sh. You will see the console output in the console window while the server initializes. You will know when the server has finished starting when you see the message WebLogic Server started in the console output.

   Note: This file defaults to the Cloudscape database. See Setting Up an Oracle Database for information about using Oracle databases.

2. Using a browser, try the example applications to make sure the server is working correctly. The example applications use the Cloudscape database and reference implementation DMS that ship with the system; therefore, you should not have to make any configuration changes to test the system. All you need to do is point your browser to the correct URL listed for each application below.

   Note: Refer to WebLogic Commerce Servers Configuration for information about making configuration changes to the system. You need to change configurations if you use a database other than Cloudscape or a DMS other than the reference implementation DMS shipped with WLCS 2.0.1. The configuration document also contains information about configuring other pieces of the system, including servlets and portals.

   You might want to leave the console window in view when testing the example applications. You can see the console output indicating that the server is hitting JSP pages, compiling the Java, and taking care of other chores.

   Note: Each page loads slowly the first time you access it because the Java compiler has to compile the page source code. Subsequent loads and refreshes of the page go much faster than the initial load.

• The MyBuyBeans sample application is included as an example of the WebLogic Commerce Servers power. The application demonstrates the commerce-based components of the system and the personalization services. You can view the source in public_html/buybeans and public_html/portals/buybeans.

  To understand how directory structures relate to the URLs, refer to Setting up servlets and new portals. To run the application, point your browser to http://<wl-host>:<port>/mpbb.

  Note: /mpbb is an entry page for the MyBuyBeans portal that requires you to log in with an existing user. You can hit http://<wl-host>:<port>/mybuybeans to go directly to the MyBuyBeans portal without logging in and then create a new user with the tools provided in the upper-right corner of the page.

  Note: <port> is the ListenPort of the running WebLogic Server set in the weblogic.properties file. The default value for ListenPort is 7601.

• View the Acme Portal example at http://<wl-host>:<port>/exampleportal. This portal demonstrates functionality of the Portal Management and User Management components.

• For personalization administration needs, point your browser to http://<wl-host>:<port>/wlpsadmin for the WebLogic Personalization Server administration tools. These tools allow you to create and manage property sets, users, rules, and portals.

1. Go through the tutorial that ships with the documentation. The tutorial extends the MyBuyBeans.com portal to include personalization services for two different user groups.

2. Begin building and deploying your own personalized applications using servlets or portals. Refer to the documentation for more information about using the system.