Bookshelf Home | Contents | Index | Search | PDF

Siebel Interactive Selling Transact Server Interface Reference > Installing Transact Server > Configure the Application Server Environment >

The WebSphere Environment

---

Complete these tasks to set up the WebSphere environment for Transact Server:

Create the Siebel directory.
Copy the Siebel property file.
Set up the WebSphere class path.
Create a Web application and Servlet.
Set up the LDAP password (optional).
Register Enterprise Java Beans (EJBs).
Create an Enterprise Application.
Enable Security Permission.
Set up the Transact database.
Set up the LDAP user group.
Set up eMail service in WebSphere.
Set up the Transact Server login.

The following discussion shows you how to complete each of these tasks.

Creating the Siebel Directory

With WebSphere 3.5, you must create a directory for the new application server when you create the application server.

To create a directory for the new application server

Create a new folder name called Siebel under <WebSphere root>/appserver/hosts/default_host/.

The Siebel folder name is the same as your application server name.

Use the same case across the entire installation because the .jsp page reference is case-sensitive.
Copy the following folders to <WebSphere root>/appserver/hosts/default_host/Siebel:
Login
Propertieseditor
transactserver (under the <transact root>/jsp directory)

Administration for Siebel Property Files

Copy Siebel.prp and Siebel_default.prp from <transact-root>/properties to <Windows root>/system32. For the UNIX platform, copy Siebel.prp and Siebel_default.prp from <transact-root>/properties to <WebSphere Root>/AppServer/bin directory.

NOTE:  Siebel does not recommend that you start WebSphere by running adminserver.bat on the Windows platform. However, if you choose to do that, you must first copy Siebel.prp and Siebel_default.prp to the directory where adminserver.bat resides.

Setting Up the WebSphere Class Path

You can set up the class path for WebSphere in two steps.

To set up the WebSphere class path

Open admin.config from <WebSphere root>/appserver/bin.
For com.ibm.ejs.sm.adminiserver.class path, add all Transact jar files as follows: com.ibm.ejs.sm.adminserver.classpath=...

<Transact root>/javalib/xalan.jar;

<Transact root>/javalib/tsIBM.jar;

<Transact root>/javalib/xerces.jar;

<Transact root>/javalib/xml.jar;

<Transact root>/javalib

Alternatively, you can add the classpath through the WAS admin console. Please refer to the IBM info center link.

The following steps are based on using the default application server. To set up a different application server, change the parameters or settings accordingly. Refer to the IBM InfoCenter for more information.

Restart the WAS Admin Server and WAS Console.

Creating a Web Application

Use the IBM WAS AdminServer to create a Web application.

To create a Web application using IBM WAS AdminServer

From the Tasks menu, select Create Web Application.
Enter Siebel in the Web Application Name field.
Click Serve Servlets by classname and then click Next.
Click Next.
Select your server node name and select Default Server/Default Servlet Engine, and then click Next.
Replace Web Application Web Path field from /webapp/Siebel to /Siebel, and then click Next.
Remove "\web" at the end of Document Root field.
Click Finish.

Creating a Servlet

Use the IBM WAS AdminServer to create a Servlet.

To create a servlet using IBM WAS AdminServer

In the left view panel, click Default Servlet Engine under Default Server, right-click on Siebel (the Web Server created in the step above), and then select Create and Servlet.
Enter SiebelTransact in the Servlet Name.
Enter com.siebel.isscda.ws.servlet.mars.RequestHandler in the Servlet name.
Click Add for Servlet Web Path List.
Append SiebelTransact after "Siebel/" in the Servlet Web Path.
Click OK.
In the left view panel, click Default Servlet Engine under Default Server, right-click on Siebel (the Web Server created in the step above), select Create and Servlet.
For LoginProcess, enter Servlet Name.
Enter com.siebel.isscda.ws.servlet.rincon.LoginProcess in the Servlet Class Name.
Click Add for Servlet Web Path List.
Append "LoginProcess" after "/Siebel/" in the Servlet Web Path.
Click OK.
In the left view panel, click Default Servlet Engine under Default Server, right-click on Siebel (the Web Server created in the step above), select Create and Servlet.
Enter Logout in the Servlet Name.
Enter com.siebel.isscda.ws.servlet.rincon.Logout in the Servlet Class Name.
Click Add for Servlet Web Path List.
Append "Logout" after "/Siebel/" in the Servlet Web Path.
Click OK.

Setting Up the LDAP Password

At this point, if you are going to use an LDAP server, you need to set up an LDAP password.

To set up the LDAP password

Copy the propertieseditor folder from <transact root>/jsp to <Web Server>/<docs root>.
Open index.htm file. Change from "src=/common.jsp" to "src =

/Siebel/propertieseditor/common.jsp."

Make sure the HTTP server is up and running.
Start the default application server from the console.
Open a browser and enter http://<hostname>/propertieseditor/index.htm to modify the LDAP Credential from the Authentication page.
Enter your LDAP password and click Submit.

Register EJBS

Before users can continue to create an application server for Transact, they must check whether or not the JDBC driver and data source are installed and set up correctly. For information on installing and setting up JDBC and data source, refer to Additional Tasks.

To create EJBs

Link DataSource to the application server.
In the left view panel, click Default Server.
Select Default Container.
In the right view panel, select Data Source.
Click Change.
Select the correct DataSource.
Click Apply.
Create EJBs.
In the left view panel, select Default Server, right-click on Default Container, and then select Create and EnterpriseBean.
Enter the Java bean name (Siebel prefix is recommended).
Click Browse and select tsIBM.jar from <transact root>/javalib.
Click Deploy and Enable WLM.

A significant amount of time is required to create all the Java beans.

After the bean has been deployed, you can set up the database to enable table creation for the CMP bean from the console; or, you can perform this setup at a later time. Refer to the IBM information center document for more information.
Two types of Java beans are created: CMP beans and Session beans.

CMP beans are OLKeySequencer, OLSession, OLAppData, OLItem, OLQuote, OLPackage, and OLGenericElem. Usually, "create table" is checked from the default setup for all the CMP beans. However, Siebel Systems recommends that you check if "Create Table" is marked for all the CMP beans. To see the database setup, click EJB and in the right panel click "DataSource."

Select OLKeySequencerHome and click the General tab from the right panel.
Change the Database Access from "Shared" to "Exclusive," and then apply this change.

Creating an Enterprise Application

Use the IBM WAS AdminServer to create an Enterprise application.

To create an enterprise application using IBM WAS AdminServer

Select Create Enterprise Application from the Tasks menu.
Enter ISSCDA in the Enterprise Application.
Select the EJBs created in the previous section.
Highlight the beans, and then click Add.
Select Siebel, which is the Web Server created in the previous procedure.
Click Finish.

Enabling Security Permission

Use the IBM WAS AdminServer to enable security permission.

To enable security permission using IBM WAS AdminServer

Enable Global Security.
Use the IBM WS AdminServer to Enable Global Security.
Select Configure Global Security from the Tasks menu.
Select Enable Security, and then click Next.
Select Basic (User ID and Password), and then click Next.
Select Lightweight Third Party Authentication, and then click Next.
Under User Register, provide the required information, and then click Finish.

Examples of input values:

Security ServerID: <valid user in LDAP>/Security Server

Password: <user password>/Directory

Type: Netscape/Host: <ldap host name>/Port:389/Base Distinguished

Name: ou=People, o=<domain name>.

Click Finish.
Enter an LTPA password.
Click Finish.
Enable Resource Security.

Select Configure Resource Security from the Tasks menu.

Enterprise Beans
Click Enterprise Beans.
Select a Transact EJB, and then click Next.
Use the Default method.
Highlight all the methods from the EJB, and then click Finish.
Repeat to configure all the EJBs.
Virtual Hosts
Click Virtual Hosts.
Select default_host, and then click Next.
Select a Transact servlet.
Use the Default method.
Select all methods, and then click Finish.
Repeat to configure for all the Transact servlets.
Enable Security Permission.

Select Configure Security Permission from the Tasks menu.

Select ISSCDA, the Enterprise Application created in the previous procedure, and then click Next.
Highlight all the methods, and then click Next.
Select EveryOne to enable the security for everyone.
Click Finish.

In order for these security changes to take effect, you must restart the IBM WAS AdminServer.

Set Up the Transact Database

The Transact database tables can reside in a DB2 or Oracle database instance.

DB2 Database Instance

You must alter the DB2 tables to set up the Transact database.

Once the application server starts, you must run the two scripts provided that alter the Transact tables in the DB2 database.
Run tsDB2.sql to update the Transact tables.

Oracle Database Instance

You must alter the Oracle tables to set up the Transact database.

Once the application server starts, you must run the two scripts provided that alter the Transact tables in the Oracle database.
Run tsORACLE. sql to update the Transact tables.

Setting Up the LDAP User Group

If you choose to use an LDAP server, then you must set up the LDAP user group.

To set up the LDAP user group (optional)

Run setRinconPath.bat from <Transact root>/scripts for Windows platform.
Copy Siebel.prp and Siebel_default.prp from <Windows root>/system32 to <Transact root>/Scripts for Windows platform.
Copy Siebel.prp and Siebel_default.prp from <WebSphere Root>/AppServer/bin to <Transact root>/Scripts for UNIX platform.
Default Rincon script only provides system/guest as default users. You must use Rincon_add_user.sci script to add more users.
Run Rincon_setup.bat for the first time setup for the Windows platform, or run Rincon_setup.sh for UNIX platform.
Before you can add LDAP users, you have to modify rincon_add_user.sci. (If you do not want to add new users, you can skip this step.)
Run rincon_run.bat to add new users for Windows platform, or run Rincon_run.sh for UNIX platform.
Run transact_setup.bat to set address and group information for users from the Windows platform, or run transact_setup.sh for UNIX platform.

Setting Up eMail Service

To set up an eMail service, you must install a package that supports Java mail.

To set up eMail Service

Install any package that supports Java Mail 1.1 API.
Set up the class path to reference the Java Mail Package.
Open the property editor to change the email_enable_flag to "on."
Restart the WebSphere server.

Setting Up the Transact Server Login

You can set up the Transact Server login in two steps.

To set up the Transact Server login

Open the LoginPage.jsp from

<WebSphere root>/appserver/hosts/default_host/Siebel/login. Change "action=/LoginProcess" to "action=/Siebel/LoginProcess."

Modify "ShoppingCart.jsp" to update the line "<script src="http://<web host name>/<your application folder>/jd/header.js"></script>" with the correct URL.

Bookshelf Home | Contents | Index | Search | PDF