IBM 4.6.x User Manual

IBM WebSp here Business Integration Adapters



Adapter for Sie be l eBusiness Applications
User Gui d e

Adapter Ve r s i o n 4. 6.x

IBM WebSp here Business Integration Adapters



Adapter for Sie be l eBusiness Applications
User Gui d e

Adapter Ve r s i o n 4. 6.x

To

©

US

Note!

Before using this information and the product it supports, read the information in “Notices” on page 123

30September2004

This edition of this document applies to WebSphere Business Integration Adapter for Siebel eBusiness Applications
(5724-H43), Version 4.6.

send us your comments about this document, e-mail [e-mail]. We look forward to hearing

from you.

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1997, 2004. All rights reserved.

Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

©

Contents

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

What this document includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

What this document does not include . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi

New in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

New in release 4.6.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

New in release 4.5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

New in release 4.4.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

New in release 4.3.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

New in release 4.2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

New in release 4.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

New in release 4.0.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Siebel application architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Connector architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

How the connector works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Chapter 2. Installing the adapter . . . . . . . . . . . . . . . . . . . . . . . . .9

Adapter environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Installing the adapter and related files . . . . . . . . . . . . . . . . . . . . . . . . . .11

Verifying an installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Event and archive tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Chapter 3. Configuring the connector . . . . . . . . . . . . . . . . . . . . . .19

Overview of Connector Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Starting Connector Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Running Configurator from System Manager . . . . . . . . . . . . . . . . . . . . . . . .21

Creating a connector-specific property template . . . . . . . . . . . . . . . . . . . . . . .21

Creating a new configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Using an existing file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Completing a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Setting the configuration file properties . . . . . . . . . . . . . . . . . . . . . . . . . .27

Saving your configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Changing a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Completing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Using Connector Configurator in a globalized environment . . . . . . . . . . . . . . . . . . .35

Chapter 4. Understanding business objects . . . . . . . . . . . . . . . . . . . .37

Business object structure and relationships . . . . . . . . . . . . . . . . . . . . . . . . .37

Business object application-specific information . . . . . . . . . . . . . . . . . . . . . . .39

Chapter 5. Creating business objects . . . . . . . . . . . . . . . . . . . . . .49

Modifying business object samples . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Overview of Siebel ODA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Installing and using Siebel ODA . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Using SiebelODA in Business Object Designer . . . . . . . . . . . . . . . . . . . . . . . .56

Reviewing the generated definition . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Adding information to the business object definition . . . . . . . . . . . . . . . . . . . . .70

Copyright IBM Corp. 1997, 2004

iii

iv

Chapter 6. Using the adapter with Siebel business services . . . . . . . . . . . . .73

Understanding business services . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Verb processing with business services . . . . . . . . . . . . . . . . . . . . . . . . . .75

Events detection with business services . . . . . . . . . . . . . . . . . . . . . . . . . .76

Custom business service support . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Chapter 7. Running the connector . . . . . . . . . . . . . . . . . . . . . . . .79

Starting the connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Stopping the connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Chapter 8. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . .81

MAX_LOG_FILE_SIZE error on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . .81

Decreasing the size of the Siebel log file . . . . . . . . . . . . . . . . . . . . . . . . . .81

Memory limitations with result set support . . . . . . . . . . . . . . . . . . . . . . . . .81

Appendix A. Standard configuration properties for connectors . . . . . . . . . . .83

New properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Standard connector properties overview . . . . . . . . . . . . . . . . . . . . . . . . . .83

Standard properties quick-reference . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Standard properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Appendix B. Connector specific properties . . . . . . . . . . . . . . . . . . . 107

ApplicationPassword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

ApplicationUserName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

ArchiveProcessed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

ConnectErrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

ConnectorID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

ConnectString . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

DataBeanPoolSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

DataBeanRefreshInterval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

EventProcessingSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

PollAttributeDelimiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

PollQuantity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

ResonateSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

SiebelLanguageCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

SiebelVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

SupportNameValuePair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

UseDefaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

ViewMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Appendix C. Common Event Infrastructure . . . . . . . . . . . . . . . . . . . .113

Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Enabling Common Event Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . .113

Obtaining Common Event Infrastructure adapter events . . . . . . . . . . . . . . . . . . . .113

For more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Common Event Infrastructure event catalog definitions . . . . . . . . . . . . . . . . . . . .114

XML format for “start adapter” metadata . . . . . . . . . . . . . . . . . . . . . . . . .114

XML format for ″stop adapter″ metadata . . . . . . . . . . . . . . . . . . . . . . . . .116

XML format for “timeout adapter” metadata . . . . . . . . . . . . . . . . . . . . . . . .116

XML format for ″request″ or ″delivery″ metadata . . . . . . . . . . . . . . . . . . . . . .117

Appendix D. Application Response Management . . . . . . . . . . . . . . . . .119

Application Response Measurement instrumentation support . . . . . . . . . . . . . . . . . .119

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Programming interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Trademarks and service marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Adapter for Siebel eBusiness Applications User Guide

in

v

v

v

v

v

If

or

©

About this document

The IBM

R

WebSphere

R

Business Integration Adapter portfolio supplies integration
connectivity for leading e-business technologies, enterprise applications, and legacy
and mainframe systems. The product set includes tools and templates for
customizing, creating, and managing components for business integration.

What this document includes

This document describes installation, connector property configuration, business
object development, and troubleshooting for the IBM WebSphere Business
Integration Adapter for Siebel eBusiness Applications.

What this document does not include

This document does not describe deployment metrics and capacity planning issues
such as server load balancing, number of adapter processing threads, maximum
and minimum throughputs, and tolerance thresholds.

Such issues are unique to every customer deployment and must be measured
within or close to the exact environment where the adapter is to be deployed. You
should contact your IBM services representative to discuss the configuration of
your deployment site, and for details on planning and evaluating these kinds of
metrics, given your specific configuration.

Audience

This document is for WebSphere business integration system consultants and
customers. To use the information in this document, you should be knowledgeable

the following areas:

Connector development

Business object development

Siebel application architecture

Siebel Tools

Visual Basic

Note:

Related documents

The complete set of documentation available with this product describes the
features and components common to all WebSphere Business Integration Adapters
installations, and includes reference material on specific components.

This document contains many references to two other documents: the System
Installation Guide for Windows
WebSphere InterChange Server. If you choose to print this document, you may
want to print these documents as well.

you are a consultant or customer located in Japan and are using Siebel

2000, you must use the Adapter for Siebel 2000 User Guide.

®

for UNIX

®

and the Implementation Guide for

You can install documentation from the following sites:

Copyright IBM Corp. 1997, 2004

v

v

v

v

A

vi

v

For general adapter information; for using adapters with WebSphere message
brokers (WebSphere MQ Integrator, WebSphere MQ Integrator Broker,
WebSphere Business Integration Message Broker); and for using adapters with
WebSphere Application Server:

http://www.ibm.com/websphere/integration/wbiadapters/infocenter

For using adapters with InterChange Server:

http://www.ibm.com/websphere/integration/wicserver/infocenter

http://www.ibm.com/websphere/integration/wbicollaborations/infocenter

For more information about message brokers (WebSphere MQ Integrator Broker,
WebSphere MQ Integrator, and WebSphere Business Integration Message
Broker):

http://www.ibm.com/software/integration/mqfamily/library/manualsa/.

For more information about WebSphere Application Server:

http://www.ibm.com/software/webservers/appserv/library.html

These sites contain simple directions for downloading, installing, and viewing the
documentation.

Note: Important information about this product <<or “the products documented in

this guide” or whatever works for your doc>> may be available in Technical
Support Technotes and Flashes issued after this document was published.
These can be found on the WebSphere Business Integration Support Web
site, http://www.ibm.com/software/integration/websphere/support/.
Select the component area of interest and browse the Technotes and Flashes
sections.

Typographic conventions

This document uses the following conventions:

courier font

bold

italic, italic
blue outline

ProductDir

Indicates a literal value, such as a command name, file
name, information that you type, or information that the
system prints on the screen.

Indicates a new term the first time that it appears.
Indicates a variable name or a cross-reference.

blue outline, which is visible only when you view the
manual online, indicates a cross-reference hyperlink. Click
inside the outline to jump to the object of the reference.

Represents the directory where the product is installed.

Adapter for Siebel eBusiness Applications User Guide

v

v

v

v

v

v

v

–

–

©

New in this release

New in release 4.6.x

Updated in September, 2004

This guide has been updated to include the following changes:

The adapter supports Siebel version 7.7.

Adapter support for Siebel version 7.7 is provided on two additional platforms:
Solaris 9.0 and Windows 2003.

The adapter is modified so that it can process business services where the
request contains only simple attributes and no SiebelMessage container attribute.

Support for result set retrieval, which is enabled only with specific versions of

®

DB2
versions, refer to the DB2 Information Integrator product documentation.)

Information Integrator broker. (For information about these specific

New in release 4.5.x

Updated in June, 2004. Beginning with version 4.5.x, the Adapter for Siebel
eBusiness Applications is no longer supported on Solaris 7, so references to that
platform have been removed from this guide.

New in release 4.4.x

February 2004

The adapter supports retrieval of multiple records using wrapper objects and the

RetrievebyContent verb.

December 2003

This guide has been updated to include the major changes listed below:

The adapter now supports custom-written business services.

Support for the generation of WebSphere Business Integration business object
definitions for custom business services is added to the Object Discovery Agent
(ODA). The generation process is similar to that of Siebel business objects and
components.

Two new configuration properties, EventProcessingSupport and SiebelVersion,
have been added.

EventProcessingSupport can be used to switch off subscription delivery if
necessary and takes a value of true or false, with the default value being true.

SiebelVersion enables the adapter to run against a specified version of the
Siebel application while preventing it from accessing the Schema Version
Siebel business object and business component. Valid values are 6 or 7, and
the default value is NONE. Use of the default value is recommended.

The Siebel business components CW Events and CW Archive have been

v

renamed IBM Events and IBM Archive. The adapter uses these components as it
did in earlier versions. For backward compatibility, the adapter works with both
the old and new component names. For example, the adapter will check first for
IBM Events, and if found it will use it as the event store. If IBM Events is not

Copyright IBM Corp. 1997, 2004

vii

an

9.

v

v

v

v An

v

v

v

–

–

–

found, the adapter will check for CW Events. If it does not find either, and the
adapter is configured for subscription delivery, it will return an error and
terminate.

Note:

New in release 4.3.x

Updated in July, 2003. The adapter can now use WebSphere Application Server as

integration broker. For further information, see “Adapter environment” on page

The adapter now runs on the following platforms:

Solaris 7,8

AIX

HP-UX 11i

New in release 4.2.x

Updated in March, 2003. The “CrossWorlds” name is no longer used to describe an
entire system or to modify the names of components or tools, which are otherwise
mostly the same as before. For example “CrossWorlds System Manager” is now
“System Manager,” and “CrossWorlds
InterChange Server.”

The changes to this version of the connector support Siebel, version 7.5 and the
Siebel connectivity DLL.

Adapter installation information has been removed from this guide. See
Chapter 2 for the new location of that information.

®

5.x

®

InterChange Server” is now “WebSphere

New in release 4.1.x

The connector delivered with IBM WebSphere Business Integration Adapter for
Siebel eBusiness Applications has been internationalized. For more information, see
“Processing locale-dependent data” on page 7 and Appendix A, “Standard
configuration properties for connectors,” on page 83

New in release 4.0.x

The IBM WebSphere business integration adapter for Siebel eBusiness Applications
includes the connector for Siebel eBusiness Applications. This adapter operates
with both the InterChange Server (ICS) and WebSphere MQ Integrator integration
brokers. An integration broker, which is an application that performs integration of
heterogeneous sets of applications, provides services that include data routing. This
adapter includes:

SiebelODA

Sample business objects

IBM WebSphere Adapter Framework, which consists of:

Connector Framework

Development tools (including Business Object Designer and Connector
Configurator)

APIs (including ODK, JCDK, and CDK)

application-component specific to Siebel eBusiness Applications

manual provides information about using this adapter with both integration

This
brokers: InterChange Server (ICS) and WebSphere MQ Integrator.

viii

Adapter for Siebel eBusiness Applications User Guide

Important: Because the connector has not been internationalized, do not run it

against InterChange Server version 4.1.1 if you cannot guarantee that
only ISO Latin-1 data will be processed.

New in this release

ix

x

Adapter for Siebel eBusiness Applications User Guide

v

v

v

v

v

v

v

v

v

v

v

v

v

v

v

v

©

Chapter 1. Overview

“Terminology”

“Siebel application architecture” on page 2

“Connector architecture” on page 3

“Business object processing” on page 4

“Event management” on page 6

“Handling lost connections to the Siebel application” on page 7

“Processing locale-dependent data” on page 7

“Common Event Infrastructure” on page 8

“Application Response Measurement” on page 8

This chapter provides an overview of adapter terminology and the WebSphere
Business Integration Adapter for Siebel eBusiness Applications. It is important that
you understand the topics in this chapter before you attempt to install, configure,
and use the adapter.

Terminology

Note: This chapter includes references to Event and Archive business components,

business objects, and tables. These references are synonymous with
references to CW Event and CW Archive that appear in earlier versions, and
with references to IBM Event and IBM Archive that appear in Siebel 7.5

The following terms are used in this document.

adapter

The component in the WebSphere business integration system that
provides components to support communication between an integration
broker and either an application or a technology. An adapter always
includes a connector, message files, and configuration tools. It can also
include an Object Discovery Agent (ODA) or a data handler.

adapter framework

The software that IBM provides to configure and run an adapter. The
runtime components of the adapter framework include the Java

™

runtime
environment, the connector framework, and the Object Discovery Agent
(ODA) runtime. This connector framework includes the connector libraries
(C++ and Java) needed to develop new connectors. The ODA runtime
includes the library in the Object Development Kit (ODK) needed to
develop new ODAs. The configuration components include the following
tools:

Business Object Designer,

Connector Configurator,

Log Viewer,

System Manager,

Adapter Monitor,

Test Connector

and, optionally, any Object Discovery Agents (ODAs) associated with an
adapter.

Copyright IBM Corp. 1997, 2004

1

A

to a

An

v

v

v

2

Adapter Development Kit (ADK)

development kit that provides some samples for adapter development,

including sample connectors and Object Discovery Agents (ODAs).

connector

The component of an adapter that uses business objects to send
information about an event to an integration broker (event notification) or
receive information about a request from the integration broker (request
processing). A connector consists of the connector framework and the
connector’s application-specific component.

connector framework

The component of a connector that manages interactions between a
connector’s application-specific component and the integration broker. This
component provides all required management services and retrieves the
meta-data that the connector requires from the repository. The connector
framework, whose code is common to all connectors, is written in Java and
includes a C++ extension to support application-specific components
written in C++.

connector controller

The subcomponent of the connector framework that interacts with
collaborations. A connector controller runs within InterChange Server and
initiates mapping between application-specific and generic business objects,
and manages collaboration subscriptions to business object definitions.

integration broker

The component in the WebSphere business integration system that
integrates data among heterogeneous applications. An integration broker
typically provides a variety of services that include: the ability to route
data, a repository of rules that govern the integration process, connectivity

variety of applications, and administrative capabilities that facilitate
integration. Examples of integration brokers: the WebSphere Business
Integration Message Broker; WebSphere Business InterChange Server.

WebSphere business integration system

enterprise solution that moves information among diverse sources to
perform business exchanges, and that processes and routes information
among disparate applications in the enterprise environment. The business
integration system consists of an integration broker and one or more
adapters.

Siebel application architecture

The Siebel application architecture contains three layers, as follows:

User interface objects layer--This layer contains the visual elements that the user
interacts with.

Business objects layer--This layer contains both business components and
business objects. A business component is a fundamental business entity,
consisting of multiple fields that represent it. A business object is a collection of
related business components. The Siebel connector communicates with this layer
using the Siebel Java Data Bean.

Data objects layer--This layer contains the object definitions which provide
logical representation of the underlying physical database. It is independent of
the installed relational database management system, and it is not accessible by
the Siebel Java Data Bean.

Adapter for Siebel eBusiness Applications User Guide

on

Connector architecture

The connector has been designed following the meta-data design principles as
outlined in the Connector Development Guide for Java. This means that existing
application-specific business objects can be extended and customized and new
business objects can be defined without requiring additional coding or
customization in the connector code.

The following diagram illustrates the Siebel connector architecture.

Integration broker

Siebel eBusiness application

User interface

Siebel enterprise server

Siebel client administration manager

Siebel business objects

WebSphere InterChange Server

event and archive store

Figure 1. Siebel connector architecture

How the connector works

This section describes how meta-data enhances the connector’s flexibility, and
presents a high-level description of business object processing and event
notification.

Siebel
Java
data bean

Via CW Event and

""

CW Archive usiness

"" b
components

CWConnector API

Siebel connector agent

Event
notification

BOHandler

The connector and meta-data

The connector is meta-data-driven. Meta-data is application-specific data that is
stored in business objects and that assists the connector in its interaction with the
application. A meta-data-driven connector handles each business object that it
supports based on meta-data encoded in the business object definition rather than

instructions hardcoded in the connector. A business object corresponds to a
Siebel business component. For more information about business objects, see
Chapter 6, “Using the adapter with Siebel business services,” on page 73

Business object meta-data includes the structure of a business object, the settings of
its attribute properties, and the content of its application-specific information.
Because the connector is meta-data driven, it can handle new or modified business
objects without requiring modifications to the connector code.

Chapter 1. Overview

3

To

a

to

4

Business object processing

This section provides an overview of how the connector processes integration
broker requests and application events.

Processing integration broker requests

When the connector receives a request from a business object to perform an
application operation, the connector processes hierarchical business objects
recursively; that is, it performs the same steps for each child business object until it
has processed all individual business objects.

Note: The term hierarchical business object refers to a complete business object,

including all the child business objects that it contains at any level. The term

individual business object refers to a single business object, independent of

any child business objects it might contain or that contain it. The term

top-level business object refers to the individual business object at the top of

the hierarchy that does not itself have a parent business object.

Business object retrieval:

When an integration broker asks the connector to
retrieve a hierarchical business object from the Siebel application, the connector
attempts to return a business object to the integration broker that exactly matches
the current representation of a Siebel business component instance. In other words,
all simple attributes of each individual business object returned to the integration
broker match the value of the corresponding field in the Siebel business
components.

retrieve the complete business component, the connector uses the primary key
values in the top-level business object received from the integration broker to
recursively descend through the corresponding data in the database.

Business object RetrievalByContent:

When an integration broker asks the
connector to retrieve a hierarchical business object based on values in non-key
attributes in the top-level business object, the connector uses the value of all
non-null attributes as the criteria for retrieving the data.

Business object creation:

When an integration broker asks the connector to create

hierarchical business object in the Siebel application, the connector creates all the

children of the top-level business object prior to creating the parent. An exception

this rule is when the relationship between the parent and child is a multi-value
link in Siebel and the link is inactive. In this case, the child is created after the
parent, and the keys are generated by the Siebel application.

Business object modification:

Business object modification, or updating, involves
comparing the retrieved after image of the business object from Siebel with the
inbound business object. The process involves setting the correct verb on the child
objects. If the keys are set on the parent and all other attributes are set to CxIgnore,
the parent update is skipped.

The default behavior is to compare the after image from the Siebel applications
with the inbound business object, then change the verbs on the child container
objects. This process ensures that all the children in the Siebel application are made
the same as the inbound business object. If the verb is not set on the children, the
default is set to Update.

Important: If some of the children need to be retained, the inbound object verb

must be set to DeltaUpdate, and verbs must be set on each one of the

Adapter for Siebel eBusiness Applications User Guide

a

Id of

child container objects. In this case, only these objects in the Siebel
application are processed while the others are left untouched.

Business object deletion:

When an integration broker asks the connector to delete

record, the record is removed from the underlying database. Only the parent
needs to be deleted because the Siebel DeleteCascade feature deletes all of the
children. If any of the required attributes are missing from the inbound business
object, the delete fails.

Exists verb:

The primary business component name is typically the same business
object name in Siebel. If the ObjectName and ComponentName application specific
information match, the keys are set on this business component and the query is
executed. If the record exists, it returns True; if the record does not exist, it returns
False.

Processing application events

Components:

tables in the Siebel database. You must create Event and Archive, two new Siebel
business components corresponding to these tables.

Triggering:

application can be treated as an event. Siebel supports Visual Basic scripts and
Siebel eScripts embedded in the Siebel business component event handlers to
populate the event table. On a call to pollForEvents, these event records are
obtained and processed. The Event business component stores information about
the event, as listed in Table 1

The event notification requires the creation of event and archive

The creation, update, or delete of any record in the Siebel eBusiness

Note: The information in Table 1 is used by the connector during event

subscription to build corresponding business objects and to send those
objects to the connector framework for further processing.

Table 1. Events business component structure

Fields

Object Key

Object Name
Object Verb
Priority
Status

Description
Event Id
ConnectorId

Description

The unique identifier that identifies the business object row for which the
event was created

Siebel business object for which the event was deleted
Verb for the event
Event priority
Event Status Initially, this is set to READY_FOR_POLLOther status values

include:IN_PROGRESS=1 -- The event has been picked up and is sent to the
connector framework. The connector changes the status of the event to

IN_PROGRESS after it picks the event for processing. UNSUBSCRIBED=2 -- The

event has not been subscribed for. The connector sets the status to
UNSUBSCRIBED if the isSubscribed call returns a False. SUCCESS=3 -- The

event was successfully processed by the connector framework. The connector sets
the status to SUCCESS if the event is processed successfully by the connector
framework.ERROR_PROCESSING_EVENT=-1 -- There was an error processing

the event. This status is set if there was an error while processing the
event. ERROR_POSTING_EVENT=-2 -- There was an error posting the event to
the connector framework. This status is set if the call to gotApplEvent
fails in pollForEvents. ERROR_OBJECT_NOT_FOUND=-3 -- The object for
which the event was created could not be found. This status is set if the
doVerbFor call could not find the object in pollForEvents.

Any comment associated with the event

the event row

Identifies the connector in a multiple connector configuration

Chapter 1. Overview

5

a

on

6

Table 1. Events business component structure (continued)

Fields

Event Ts

Description

Event creation timestamp

Create notification:

business object of the type specified by the event, sets the key values for the
business object (using the object key specified in the Event business component),
and retrieves the business object from the Siebel application. After it retrieves the
business object, the connector sends it with the Create verb to the integration
broker.

Update notification:

business object of the type specified by the event, sets the key values for the
business object (using the object key specified in the Event business component),
and retrieves the business object from the database. After it retrieves the business
object, the connector sends it with the Update verb to the integration broker.

Delete notification:

business object of the type specified by the event, sets the key values for the
business object (using the object key specified in the Event business component),
and sends it with the Delete verb to the integration broker. All values other than
the key values are set to CxIgnore.

Retrieving business objects for event processing:

processing is based on both key and non-key attributes. It is mandatory that the
business object support the RetrieveByContent verb.

Event management

The connector’s event detection mechanism uses a Event business component and

Archive business component. Because there are potential failure points associated
with the processing of events, the event management process does not delete an
event from the Event business component until it has been inserted it into the
Archive business component.

When the connector encounters a Create event, it creates a

When the connector encounters an Update event, it creates a

When the connector encounters a Delete event, it creates a

Retrieval of objects for event

The connector polls the Event business component at a regular, configurable
interval, retrieves the events, and processes the events first by priority and then
sequentially. When the connector has processed an event, the event’s status is
updated appropriately.

The setting of its ArchiveProcessed property determines whether the connector
archives an event into the Archive business component after updating its status.
For more information on the ArchiveProcessed property, see “ArchiveProcessed”

page 109.

Table 2 illustrates the archiving behavior depending on the setting of the
ArchiveProcessed property.

Table 2. Archiving behavior

Archive processed
setting

true or no value

Adapter for Siebel eBusiness Applications User Guide

Event processing status

Successful

Unsuccessful

Connector behavior

Event is deleted from the Events
business component and archived
with status of Success

Archived with status of Error

No

in

No

of

v If

v If

v If

v

v

v

Table 2. Archiving behavior (continued)

Archive processed
setting

Event processing status

subscription for business

object

Connector behavior

Event is deleted from the Events
business component and archived
with one of the following statuses:

Error Processing Event Error
Posting Event Error Object Not
Found

false

Successful

Not archived and remains in the
Events business component with a
status of Success

Unsuccessful

Event is not archived and remains

the Events business component
with one of the following
statuses: Error Processing Event

Error Posting Event Error Object
Not Found

subscription for business

object

Remains in event table with status

Unsubscribed

Smart filtering

Duplicate events are not saved in the event store. Before storing a new event as a
record in the event store, the VB Script or eScript needs to query the event store
for existing events that match the new event. The event detection mechanism does
not generate a record for a new event in the following cases:

the business object name, verb, status, and ConnectorId (if applicable) in a

new event match those of another unprocessed event in the event store.

the business object name, key, and status for a new event match an
unprocessed event in the event table, and the verb for the new event is Update
while the verb for the unprocessed event is Create.

the business object name, key, and status for a new event match an
unprocessed event in the event table, and the verb in the unprocessed event in
the event table is Create while the new verb is Delete. In this case, remove the
Create record from the event store.

Handling lost connections to the Siebel application

The connector terminates when an error message specified in the ConnectErrors
connector property is detected. The text from ConnectErrors in compared with the
Siebel error message. If a match is found, the connector returns
AppResponseTimeOut, which terminates the connector.

The ConnectErrors message can be returned by the Siebel application if the
connection is lost and the connector tries to:

Access the Event and Archive business components

Retrieve the business object that is related to the event

Create or update a record pertaining to a business object.

Processing locale-dependent data

The connector has been internationalized so that it can support double-byte
character sets, and deliver message text in the specified language. When the
connector transfers data from a location that uses one character code set to a
location that uses a different code set, it performs character conversion to preserve

Chapter 1. Overview

7

is

8

the meaning of the data. The Java runtime environment within the Java Virtual
Machine (JVM) represents data in the Unicode character code set. Unicode contains
encodings for characters in most known character code sets (both single-byte and
multibyte). Most components in the WebSphere business integration system are
written in Java. Therefore, when data is transferred between most Server Access
components, there is no need for character conversion. To log error and
informational messages in the appropriate language and for the appropriate
country or territory, configure the Locale standard configuration property for your
environment. For more information on these properties, see Appendix A, “Standard
configuration properties for connectors,” on page 83

Common Event Infrastructure

This adapter is compatible with the IBMs Common Event Infrastructure, a
standard for event management that permits interoperability with other IBM
WebSphere event-producing applications. If Common Event Infrastructure support

enabled, events produced by the adapter can be received (or used) by another

Common Event Infrastructure-compatible application.

For more information refer to the Common Event Infrastructure appendix in this
guide.

Application Response Measurement

This adapter is compatible with the Application Response Measurement
application programming interface (API), an API that allows applications to be
managed for availability, service level agreements, and capacity planning. An
ARM-instrumented application can participate in IBM Tivoli
Transaction Performance, allowing collection and review of data concerning
transaction metrics.

For more information refer to the Application Response Measurement appendix in
this guide.

®

Monitoring for

Adapter for Siebel eBusiness Applications User Guide

v

v

v

v

v

v

v

v

v

v

v

In

v

v

v

v

©

Chapter 2. Installing the adapter

“Adapter environment”

“Installing the adapter and related files” on page 11

“Verifying an installation” on page 11

“Event and archive tables” on page 12

chapter describes how to install the WebSphere

This
for Siebel eBusiness Applications.

Note: This chapter includes references to Event and Archive business components,

business objects, and tables. These references are synonymous with
references to CW Event and CW Archive that appear in earlier versions, and
with references to IBM

Adapter environment

Before you can install, configure, and run an adapter, you must understand its
environmental requirements.

Broker compatibility

This adapter runs with the WebSphere Business Integration Adapter
FrameworkV2.6 and requires one of the following:

WebSphere InterChange ServerV4.2.2,V4.3

WebSphere MQ IntegratorV2.1

WebSphere MQ Integrator BrokerV2.1

WebSphere Business Integration Message BrokerV5.0.1

WebSphere Application Server EnterpriseV5.0.2, in conjunction with WebSphere
Studio Application Developer Integration EditionV5.0.1

WebSphere Business Integration Server FoundationV5.1.1

DB2 Information IntegratorV8.2.3 - supported by WebSphere Business
Integration Adapters for mySAP.com, PeopleSoft, and Siebel only.

®

Business Integration Adapter

®

Event and IBM Archive that appear in Siebel 7.5

Adapter platforms

addition to a broker, this adapter requires one of the following operating

systems:

All operating system environments require the Java compiler (IBM JDK 1.4.2for
Windows 2000) for compiling custom adapters

AIX:

AIX 5.1 with Maintenance Level 4
AIX 5.2 with Maintenance Level 1. This adapter supports 32-bit JVM on a 64-bit
platform.

Solaris:

Solaris 8 (2.8) with Solaris Patch Cluster dated Feb. 11, 2004 or later
Solaris 9 (2.9) with Solaris Patch Cluster dated February 11, 2004 or later. This
adapter supports 32-bit JVM on a 64-bit platform.

HP-UX:

HP-UX 11.i (11.11) with June 2003 GOLDBASE11i and June 2003 GOLDAPPS11i
bundles

Copyright IBM Corp. 1997, 2004

9

v

be

v

be

v

v

v

v

v

v

v

v

v

10

v

Windows:

Windows 2000 (Professional, Server, or Advanced Server) with Service Pack 4
Windows XP with Service Pack 1A, for WebSphere Business Integration Adapter
Framework (administrative tools only)
Windows 2003 (Standard Edition or Enterprise Edition)

Adapter dependencies

Before you use the connector, you must do the following:

Install the Siebel 6.2.x, Siebel 7.0.x, Siebel 7.5.x, or Siebel 7.7x .jar files that will

used.

Verify the existence of a user account in the application. This user account must

the same as the user specified in the Siebel scripts for event creation in Siebel

Tools.

Copy the Siebel Connector.txt file from the

%ProductDir%/connectors/messages/Siebel directory to the
%ProductDir%/connectors/messagesdirectory

User setup

Before installing the connector, you must create a user account for the connector in
Siebel. This user account should have full access privileges, and the login name
should be the same as the ApplicationUserName configuration property. The default
value for the user account login name and password is CWCONN.

When installing the connector, be sure to install the files from one of the following
lists to the %ProductDir%/Connectors/Siebel/dependencies directory. The files are
located on either Siebel 6 or Siebel 7 server.

Important: The start_Siebel.bat file in the %ProductDir%/Connectors/Siebel

directory currently has the English and Japanese Siebel .jar files in the
JCLASSES variable. This is added to the CLASSPATH. For any other
language supported by Siebel, the corresponding .jar file must be
added to the JCLASSES variable.

Siebel 6

SiebelDataBean.jar

SiebelTC_enu.jar

SiebelTcCommon.jar

SiebelTcOM.jar

Siebel

7.0x or 7.5x

SiebelJI_Common.jar

SiebelJI_enu.jar

Siebel

7.7

Siebel.jar

SiebelJI_enu.jar

Adapter for Siebel eBusiness Applications User Guide

To

To

Installing the adapter and related files

For information on installing WebSphere Business Integration adapter products,
refer to the Installing WebSphere Business Integration Adapters guide located in the
WebSphere Business Integration Adapters Infocenter at the following site:

http://www.ibm.com/websphere/integration/wbiadapters/infocenter

Verifying an installation

This section describes the file structures after the product has been installed on a
UNIX or Windows system.

Verifying installed files on a UNIX system

verify the installation on a UNIX system, compare the files in the directory
where you installed the adapter to those listed in table 3. Table 3 describes the
UNIX file structure used by the connector.

Table 3. Installed UNIX file structure for the connector

Subdirectory of $ProductDir

connectors/Siebel

Description

Contains the CWSiebel.jar and the

start_Siebel.sh files for the adapter. The startup

script for the Siebel adapter is called from the
generic connector manager script. When you click
Install from the Connector Configurator,
WebSphere MQ Integrator Broker as the
integration broker, or the Connector
Configuration screen of System Manager (ICS as
the integration broker), the Installer creates a
customized wrapper for this connector manager
script. When the connector works with ICS, use
this customized wrapper to start and stop the
connector. When the connector works with
WebSphere MQ Integrator Broker, use this
customized wrapper only to start the connector;
use mqsiremotestopadapter to stop the connector.

connectors/Siebel/dependencies

Contains the patch files for event management in
the Siebel eBusiness application. Should also
contain the siebel .jar files used by the Siebel
connector.

connectors/messages/Siebel

Contains the relevant message file,

SiebelConnector.txt.

connectors/Siebel/Samples/Repository Contains the following BO samples:

Siebel_BCAccount Siebel_BCQuote
Siebel_BCContact Siebel_BCInternalProduct

Siebel_BCAsset
repository/Siebel
/lib
/bin

Contains the CN_Siebel.txt file.

Contains the WBIA. jar file.

Contains the CWConnEnv.sh file.

Verifying installed files on a Windows system

verify the installation on a Windows system, compare the files in the directory
where you installed the adapter to those listed in Table 4.Table 4 describes the
Windows file structure used by the connector.

Chapter 2. Installing the adapter

11

in

v

v

v

to

To

to

v

12

Table 4. Installed Windows file structure for the connector

Subdirectory of %ProductDir%

\connectors\Siebel

Description

Contains the connector CWSiebel.jar and the

start_Siebel.bat files.

\connectors\Siebel\dependencies

Contains the patch files for event management

the Siebel eBusiness applications. This folder

should also contain the Siebel .jar files.

\connectors\messages

Contains the relevant message file,

SiebelConnector.txt

\connectors\Siebel\Samples\Repository Contains the following BO samples:

Siebel_BCAccount Siebel_BCQuote
Siebel_BCContact Siebel_BCInternalProduct

Siebel_BCAsset
\repository\Siebel\
\lib
\bin

Contains the CN_Siebel.xsd file.

Contains the WBIA. jar file.

Contains the CWConnEnv.bat file.

Installer adds an icon for the connector file to the WebSphere business integration
menu. For a fast way to start the connector, create a shortcut to this file on the
desktop.

Note: For more information on WebSphere business integration Installer, refer to

the System Installation Guide for Windows or for Unix.

Event and archive tables

The connector uses the event table to queue events for pickup. If you have set the
ArchiveProcessed property to true or to no value, the connector uses the archive
table to store events after updating their status in the event table.

For each event, the connector gets the business object’s name, verb, and key from
the Event business component. The connector uses this information to retrieve the
entire entity from the application. If the entity was changed after the event was
first logged, the connector gets the initial event and all subsequent changes. In
other words, if an entity is created and updated before the connector gets it from
the event table, the connector gets both data changes in the single retrieval.

The following three outcomes are possible for each event processed by a connector:

Event was processed successfully

Event was not processed successfully

Event was not subscribed to

events are not deleted from the event table after the connector picks them up,

If
they occupy unnecessary space there. However, if they are deleted, all events that
are not processed are lost and you cannot audit the event processing. Therefore,
you should also create an archive table and keep the ArchiveProcessed property set

true. Whenever an event is deleted from the event table, the connector inserts it

into the archive table.

Configuring event and archive processing

configure event and archive processing, you must use configuration properties

specify the following information:

The interval frequency

Adapter for Siebel eBusiness Applications User Guide

v

v

To

1.

v

v

2.

v

v

v

v

v

v

3.

4.

v

v

v

v

v

v

v

5.

a.

v

The number of events for each polling interval

Whether the connector archives unsubscribed and unprocessed events

The unique ID of the connector, which is important when multiple connectors
poll the same table

Creating the event and archive tables in Siebel, versions 7.5 and 7.7

This procedure uses the Siebel Sales Enterprise application as an example.
Substitute all references to Siebel Sales Enterprise with the name of the Siebel
application in use.

create the event and archive tables and to trigger the business objects, perform

the following procedure:

Ensure that all current projects have been checked in, including:

Siebel Sales Enterprise project

Projects that include objects that you want to modify, such as the Account
project

Ensure that the projects are locked on both the local and development

Note:

servers.

Apply the six patch files in the following order to your local database:

ibmtable.sif
ibmview.sif
ibmapplet.sif
ibmbo.sif
ibmbc.sif
ibmcreen.sif

When you apply WebSphere business integration system patch files in a
Japanese environment, edit all the patch files as follows:

Edit the first line of each file from:

<xml version=”1.0” encoding=”windows-1252”?>

to:

<xml version=”1.0” encoding=”Shift_JPN”?>

Replace all instances of the “ENU” language setting with “JPN.” If you use the
search and replace function of your text editor, make sure you use quotation
marks around the language setting to make sure no similar words (for
example, MENU) are replaced.

When you are prompted, lock the IBM Audit project on your local database.

Ensure that the following have been created:

Two new tables, CX_IBM_ARCH_Q and CX_IBM_Event_Q

One new business object, IBM Events

One new business object, Schema version

Two new business components, IBM Archive and IBM Events

One new view, IBM Event List View

Two new applets, IBM Archive List Applet and IBM Event List Applet

One new screen IBM Events and one new screen view, IBM Event List view

Create a page tab as follows:

Access the Application > Siebel Sales Enterprise > Page tab.

Chapter 2. Installing the adapter

13

c.

d.

e.

f. Go to

6.

a.

b.

c.

d.

e.

f. Go to

7.

v If

v If

in

8.

do

9.

a.

b.

c.

d.

to

v

14

b.

Right-click and select New Record from the menu.

Enter IBM Events as the screen name and IBM Events as the text name.

For the sequence, enter a number greater than the rest of the sequence
numbers. This selection determines where the tab is displayed in the
application.

Leave the inactive field unchecked.

the Page tab locale and create a new record for IBM Events. Add ENU

for the Language Code and IBMEvents for text, if it does not exists.

Create a screen menu item as follows:

Access the Application > Siebel Sales Enterprise > Screen Menu Item.

Right-click and select New Record.

Enter IBM Events as the screen and IBM Events as the text name.

For the sequence, enter a number greater than the rest of the sequence
numbers. This selection determines where the tab is displayed in the
screen pull-down menu.

Leave the inactive field unchecked.

the screen menu item locale and create a new record for IBMEvents.

Add ENU for language and IBMEvents for text, if it does not exist.

Add or modify the Siebel VB scripts for the business components that
correspond to the business objects used at your site. The Siebel VB scripts
trigger event notification for business objects.

you want to sort events by priority, edit the priority values in the

business objects VB scripts before compiling them.

you are installing multiple connectors, set and activate the Connector Id

the VB scripts.

Apply the physical schema for the new tables to your local database. You can

this by querying for the two new tables, CX_IBM_ARCH_Q and

CX_IBM_EVENT_Q, and selecting the current query to create a physical schema.
Make sure that you leave the table space and index space blank.

Activate the new schema using the activate button.

10.

Compile the updated and locked projects on your local database to create a
new Siebel repository (.srf) file.

11.

Open Siebel Sales Enterprise on your local database. You must have
administrative privileges to perform the following:

.Create a new view called IBM Event List View. Tip: Copy the view name
from tools and paste it into the View Name field.

.Create a new responsibility called IBM Responsibility for IBM Event List
View.

.Add the employees or teams who are responsible for reviewing events to
the newly created IBM Responsibility.

.Create the CWCONN user and add it to IBM Responsibility and
Administrative Responsibility.

Test the application in your local environment. Ensure that you have visibility

12.

IBM Event List View and that an event is generated in the view after you

create a supported object. For example, create a new account in Siebel and
check that a new account event appears in the IBM Event List View.

13.

Check in the following updated and locked projects to your development
server.

IBM Audit

Adapter for Siebel eBusiness Applications User Guide

v

To

1.

2. In

To

1.

2. On

v

v

v

v

3.

v

v

v

v

v

v

v

v

v

Siebel Sales Enterprise

The project for the business objects that you want to use

Note: You should check in your locked projects only through the query.

14.

Apply the physical schema to your development database. You can do this by
querying for the two new tables, CX_IBM_ARCH_Q and CX_IBM_EVENT_Q, and
select the current query to create a physical schema. Make sure that you leave
the table space and index space blank.

15.

Activate the queried tables in the development database.

16.

Move to test and production environments accordingly.

17.

Move your newly compiled Siebel.srf file to the server.

Enable Enterprise Application Integration by going to:

Note:

Sitemap > Server Administration > Component Group and selecting Enable.

set Siebel JAVABean:

Select, Site Map->Server Admin-> Components (Sales Object Manager).

the lower applet, go to Component Parameter and enter a timeout value.

Note: The Request Timeout current value is set to 600. This means that the

connector will die after ten minutes. Based on Siebel, you can change
this value to be as large as you want.

Creating the event and archive tables in Siebel, versions below 7.5

This procedure uses the Siebel Sales Enterprise application as an example.
Substitute all references to Siebel Sales Enterprise with the name of the Siebel
application in use.

create the event and archive tables and to trigger the business objects, perform

the following procedure:

Ensure that all current projects have been checked in.

your local database, check out and lock the following files:

New Table Project

Siebel Sales Enterprise project

Projects that include objects that you want to modify, such as the Account
project

Dock project

Ensure that the projects are locked on both the local and development

Note:

servers.

Apply the seven patch files in the following order to your local database:

cwtable.sif
cwview.sif
cwapplet.sif
cwbo.sif
cwbc.sif
cwdo.sif
cwscreen.sif
schemabo.sif

Chapter 2. Installing the adapter

15

4.

5.

v

v

v

v

v

v

v

v

6.

a.

b.

c.

d.

e.

If

v If

7.

a.

b.

c.

d.

e.

If

v If

8.

16

When you apply WebSphere business integration system patch files in a
Japanese environment, edit all the patch files as follows:

Edit the first line of each file from:

<xml version=”1.0” encoding=”windows-1252”?>

to:

<xml version=”1.0” encoding=”Shift_JPN”?>

Replace all instances of the “ENU” language setting with “JPN.” If you use the
search and replace function of your text editor, make sure you use quotation
marks around the language setting to make sure no similar words (for
example, MENU) are replaced.

When you are prompted, lock the CW Audit project on your local database.

Ensure that the following have been created:

Two new tables, CX_CW_Archive_Q and CX_CW_Event_Q

One new business object, Events

One new business object, schema version

Two new business components, Archive and Events

One new view, Event List View

Two new applets, Archive List Applet and Event List Applet

One new screen Events and one new screen view, Event List view

Two new dock objects, CX_CWArchive and CX_CWEvent

Create a page tab as follows:

Access the Application > Siebel Sales Enterprise > Page tab.

Right-click and select New Record from the menu.

Enter CW Events as the screen name and IBM Events as the text name.

For the sequence, enter a number greater than the rest of the sequence
numbers. This selection determines where the tab is displayed in the
application.

Leave the inactive field unchecked.

you are using Siebel 6, proceed to Step 7.

v

you are using Siebel 7, go to the Page tab locale and create a new record
for CW Events. Add ENU for the Language Code and IBMEvents for text, if it
does not exists.

Create a screen menu item as follows:

Access the Application > Siebel Sales Enterprise > Screen Menu Item.

Right-click and select New Record.

Enter Events as the screen and IBM Events as the text name.

For the sequence, enter a number greater than the rest of the sequence
numbers. This selection determines where the tab is displayed in the
screen pull-down menu.

Leave the inactive field unchecked.

you are using Siebel 6, proceed to Step 8.

v

you are using Siebel 7, go to the screen menu item locale and create a
new record for CWEvents. Add ENU for language and IBMEvents for text, if it
does not exist.

Add or modify the Siebel VB scripts for the business components that
correspond to the business objects used at your site. The Siebel VB scripts
trigger event notification for business objects.

Adapter for Siebel eBusiness Applications User Guide

If

v If

Id in

If

VB

9.

do

a.

b.

c.

d.

to

a

a

v

v CW

v

v

v

To

1.

2. In

v

you want to sort events by priority, edit the priority values in the

business objects VB scripts before compiling them.

you are installing is multiple connectors, set and activate the Connector

the VB scripts.

Siebel 6

you want to use the Additional Object Key field, you must set it in the

script.

Apply the physical schema for the new tables to your local database. You can

this by querying for the two new tables, CX_CW_ARCHIVE_Q and

CX_CW_EVENT_Q, and selecting the current query to create a physical schema.
Make sure that you leave the table space and index space blank.

10.

Activate the new schema using the activate button.

11.

Compile the updated and locked projects on your local database to create a
new Siebel repository (.srf) file.

12.

Open Siebel Sales Enterprise on your local database. You must have
administrative privileges to perform the following:

.Create a new view called Event List View. Tip: Copy the view name from
tools and paste it into the View Name field.

.Create a new responsibility called CW Responsibility for Event List View.

.Add the employees or teams who are responsible for reviewing events to
the newly created CW Responsibility.

.Create the CWCONN user and add it to CW Responsibility and
Administrative Responsibility.

Test the application in your local environment. Ensure that you have visibility

13.

Event List View and that an event is generated in the view after you create

supported object. For example, create a new account in Siebel and check that

new account event appears in the Event List View.

14.

Check in the following updated and locked projects to your development
server.

New Table

Audit

Dock

Siebel Sales Enterprise

The project for the business objects that you want to use

You should check in your locked projects only through the query.

Note:

15.

Apply the physical schema to your development database. You can do this by
querying for the two new tables, CX_CW_ARCHIVE_Q and CX_CW_EVENT_Q, and
select the current query to create a physical schema. Make sure that you leave
the table space and index space blank.

16.

Activate the queried tables in the development database.

17.

Move to test and production environments accordingly.

18.

Move your newly compiled Siebel.srf file to the server.

Enable Enterprise Application Integration by going to:

Note:

Sitemap > Server Administration > Component Group and selecting Enable.

set Siebel JAVABean:

Select, Site Map->Server Admin-> Components (Sales Object Manager).

the lower applet, go to Component Parameter and enter a timeout value.

Chapter 2. Installing the adapter

17

18

Note: The Request Timeout current value is set to 600. This means that the

connector will die after ten minutes. Based on Siebel, you can change
this value to be as large as you want.

Adapter for Siebel eBusiness Applications User Guide