configuring siebel eai workflows

Configuring Siebel EAIWorkflows

Beta

Sun Microsystems, Inc.4150 Network CircleSanta Clara, CA 95054U.S.A.

Part No: 820–3496–06December 2007

Copyright 2008 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and withoutlimitation, these intellectual property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries.

U.S. Government Rights – Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisionsof the FAR and its supplements.

This distribution may include materials developed by third parties.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and othercountries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, the Solaris logo, the Java Coffee Cup logo, docs.sun.com, Java, and Solaris are trademarks or registered trademarks of SunMicrosystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARCInternational, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering effortsof Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox tothe Xerox Graphical User Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise comply with Sun's written licenseagreements.

Products covered by and information contained in this publication are controlled by U.S. Export Control laws and may be subject to the export or import laws inother countries. Nuclear, missile, chemical or biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Exportor reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and speciallydesignated nationals lists is strictly prohibited.

DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANYIMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TOTHE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

080916@20795

Contents

1 Configuring Siebel EAI Workflows ...................................................................................................... 5Installing the Siebel Web Server Extension .........................................................................................5

▼ To Install Siebel Web Server Extension (SWSE) .........................................................................5▼ To Verify SWSE Operation for Siebel 7 ........................................................................................7

Viewing Siebel EAI Workflow Templates ...........................................................................................8Importing Siebel Workflow Templates ............................................................................................ 12

▼ To Import the SeeBeyond Workflow Templates with Siebel 7.5 ............................................ 12Modifying Siebel Workflow Templates ............................................................................................ 13

▼ To Modify a SeeBeyond Workflow Template .......................................................................... 14Setting Up SeeBeyond Workflow Processes ..................................................................................... 14

▼ To set Up the Business Service To Execute the Workflow ...................................................... 15Creating a Subsystem for a Deployed Workflow ............................................................................. 18

▼ To Create a Subsystem For a Deployed Workflow .................................................................. 18

3

Configuring Siebel EAI Workflows

This document provides conceptual information that provides instructions on how toconfigure Siebel EAI workflows. Specifically, it provides an overview of how to install SiebelWeb Server extensions, and how to view, import, modify, and configure Workflow templates.Additionally, it describes how to create a subsystem for a deployed workflow. It includes thefollowing topics:

■ “Installing the Siebel Web Server Extension” on page 5■ “Viewing Siebel EAI Workflow Templates” on page 8■ “Importing Siebel Workflow Templates” on page 12■ “Modifying Siebel Workflow Templates” on page 13■ “Setting Up SeeBeyond Workflow Processes” on page 14■ “Creating a Subsystem for a Deployed Workflow” on page 18

Installing the Siebel Web Server ExtensionUse the following procedure to install the Siebel Web Server Extension.

▼ To Install Siebel Web Server Extension (SWSE)From the Siebel installation media, run \eappweb\setup.exe, which invokes the installationwizard.

Follow the instructions presented by the wizard. Use the naming conventions for your Siebel EAIApplication Server.

For Connection Protocol, specify the default port for an HTTP server, which is 80.

Do not use any encryption or compression methods.

1C H A P T E R 1

1

2

3

4

5

For Anonymous Employee and Anonymous Contact login and password, use SADMIN.

For Error Level for Logging, enter All Errors and Warnings. You can change this once correctsystem operation has been verified.

In the \bindirectory where you have installed the Siebel Web Server Extension, open theeapps.cfgfile and note the following (typical values are shown):[defaults]

AnonUserName = SADMIN

AnonPassword = SADMIN

AnonUserPool = 10

StatsPage = _stats.swe

[/eai]

ConnetString = siebel.TCPIP.none.none://MyGatewayServer:2320/

MyEnterpriseServer/eaiObjMgr/MyAppServerEnableExtServiceOnly = TRUE

After modifying these files, stop and then restart the following services:

■ Siebel Server■ World Wide Web Publishing Service

Log in to Siebel 7 and follow the Screens menu path:

Ctrl+Shift+A ⇒ Server Administration ⇒ Enterprise Configuration ⇒ EnterpriseComponent Groups

Select the following items, and click Enable:

■ Enterprise Application Integration■ Workflow Management■ Communication Management

Open the browser and type:yourservername/module (for example,10.1.3.135/eai)

and then click Enter.

5

6

7

8

9

10

11

Installing the Siebel Web Server Extension

Configuring Siebel EAI Workflows • December 2007 (Beta)6

Make sure that your Siebel Server ODBC data source is configured. You can verify which oneyou are using by examining the Siebel Server log directory—it contains a file listing all theparameters.

▼ To Verify SWSE Operation for Siebel 7Verify that the Server Request Processor is running correctly. You may need to synchronize theServer Request Components with the Gateway Server—follow the menu/command path:Enterprise Configuration ⇒ Batch Components Admin ⇒ Synchronize

Verify that the EAI Object Manager is running correctly.

■ Follow the path:Server Admin ⇒ Servers ⇒ Server Components

■ Under Assignment Components, select EAI Object Manager.

For Windows installations only, verify that the .swefile is associated with sweiis.dll in the website. Use the following procedure to set the association:

a. Run the IIS 4.0 Management Console application.

b. Right-click on your Web site entry in the tree display, and select Properties.

c. Select the Home Directory tab.

d. In the Application Settings box, select Configuration.

e. On the App Mappings tab, select Add.

f. Type swe, select sweiis.dll, and click OK to save the association.

Verify that the configuration files are set up properly. If LDAP is not used, comment out allLDAP-related parameters in the configuration files (for example, eai.cfg and siebel.cfg):;[SecurityAdapters]

;LDAP = LDAP

;[LDAP]

;DllName = sscfldap.dll

;ServerName =

;Port = 389

;BaseDN =

;UsernameAttributeType = uid

;PasswordAttributeType = userPassword

1

2

3

4

Installing the Siebel Web Server Extension

Chapter 1 • Configuring Siebel EAI Workflows 7

;CredentialsAttributeType = credentials

;RolesAttributeType = roles

;SslDatabase =

Note – The LDAP configuration may differ in your Siebel system depending on your version ofSiebel and your installed options. For more information on disabling LDAP in your Siebelsystem, consult your Siebel user documentation.

After modifying these files, stop and then restart the following services:

■ Siebel Server■ World Wide Web Publishing Service

Viewing Siebel EAI Workflow TemplatesUse the following procedure to view Siebel EAI workflow templates.

Following the Screens menu path shown below displays the installed Workflow templates, asshown in Figure 1–1.

Siebel Workflow Administration ⇒ Workflow Processes ⇒ All Processes

Clicking the process name to invoke a Workflow Process Designer display for that process, suchas shown in the figures below.

FIGURE 1–1 SeeBeyond Workflow Processes

5

Viewing Siebel EAI Workflow Templates


FIGURE 1–2 DELETE Workflow Template

FIGURE 1–3 QUERY Workflow Template



FIGURE 1–4 INSERT/UPDATE Workflow Template

FIGURE 1–5 EXECUTE Workflow Template



FIGURE 1–6 SEND Workflow Template

FIGURE 1–7 SEND/RECEIVE Workflow Template



Importing Siebel Workflow TemplatesUse the following procedure to import Siebel EAI workflow templates.

▼ To Import the SeeBeyond Workflow Templates withSiebel 7.5

Start Siebel EAI Client and select Siebel Sales.

Follow the menu path:

Ctrl+Shift+A ⇒ Siebel Workflow Administration ⇒ Workflow Processes

Click Import and browse to the directory that contains SeeBeyondHTTPWorkflow.xml.

This file is installed with the Enterprise Designer. If you installed the Enterprise Designer in the<c:\JavaCAPS>\edesigner directory, then the file is located in<C:\JavaCAPS>\edesigner\usrdir\modules\ext\siebeleaieway

Click Open to begin importing the Workflow template.

Check or set up the following configuration files:

■ In the file SWEApp\eapps.cfg, verify that the following section is specified correctly:

FIGURE 1–8 POST Workflow Template

1

2

3

4

5

Importing Siebel Workflow Templates


[/eai_enu]

onnectString = siebel.TCPIP.none.none://<Your Gateway Server>:2320/

<Your_Enterprise_Server>/EAIObjMgr_enu/<Your_App Server>

EnableExtServiceOnly = TRUE

WebPublicRootDir=c:<Your_Siebel_Dir>\SWEApp\public\enu

WebUpdatePassword=<Your_Password>

■ For the SiebelEAI_jcdUpsert sample, add the following sections in the filesiebsrvr\bin\ENU\eai.cfg:

[HTTP Services]

...

SEEBEYOND_HTTP_DELETE = SB_HTTP_DELETE

SEEBEYOND_HTTP_QUERY = SB_HTTP_QUERY

SEEBEYOND_HTTP_UPDATE = SB_HTTP_UPDATE

SEEBEYOND_HTTP_EXECUTE = SB_HTTP_EXECUTE

[SB_HTTP_DELETE]

Mode = Document

Service = SeeBeyond HTTP Delete

Method = RunProcess

[SB_HTTP_QUERY]

Mode = Document

Service = SeeBeyond HTTP Query

Method = RunProcess

[SB_HTTP_UPDATE]

Mode = Document

Service = SeeBeyond HTTP Update

Method = RunProcess

[SB_HTTP_EXECUTE]

Mode = Document

Service = SeeBeyond HTTP Execute

Method = RunProcess

The imported Workflow must be in active mode before it can be used; this is accomplished byclicking the active button.

Modifying Siebel Workflow TemplatesUse the following procedure to modify Siebel EAI workflow templates.

6

Modifying Siebel Workflow Templates


▼ To Modify a SeeBeyond Workflow TemplateLog in to Siebel Client 7.0, designating the appropriate Siebel server.

Follow the menu path:

Ctrl+Shift+A ⇒ Siebel Workflow Administration ⇒ Workflow Processes

Highlight the SeeBeyond Workflow Process template you want to modify.

Right-click and select Copy Record.

Rename the copied Process.

Specify the Business Object to which you want to apply the template, and any other fields thatmay be necessary (for example, Description).

After modifying a Workflow template you must create the Business Service to execute it, usingthe supplied Workflow processes as templates. This procedure is described in the followingsection.

A new Services section should be added to your siebsrvr\bin\ENU\eai.cfg file, as shown inthe preceding section.

For example, if you have a Business Service named Employee Execute, you should add thefollowing lines to the eai.cfg file:[HTTP Services]

...

EMPLOYEE_EXECUTE = EE

[EE]

Mode = Document

Service = Employee Execute

Method = RunProcess

Setting Up SeeBeyond Workflow ProcessesThe Workflow processes invoked by the SeeBeyond Workflow Templates must be set up inSiebel Business Services.

1

2

3

4

5

6

7

8

Setting Up SeeBeyond Workflow Processes


Note – The names entered in the last step above are used to set up the Business Service for thesample program supplied with the eWay. You should use them as templates to create newprocesses corresponding to the Workflows you create for your own system.

▼ To set Up the Business Service To Execute theWorkflow

Make sure the following services are running:

■ Siebel Gateway Server■ Siebel Server■ World Wide Web Publishing Service

Log in to Siebel Sales 7.0.

Follow the Screens menu path:Server Administration ⇒ Servers

Make sure that Workflow Management is Online and Enabled.

Log in to Siebel Tools 7.0 and designate the server as the database by entering sadmin, sadmin,server.

In Object Explorer, go to Siebel Objects ⇒ Project and lock the Project (see the figure below).

1

2

3

4

5

6



In Object Explorer, go to Business Service, make a copy of Workflow Process Manager (menupath Edit ⇒ Copy Record).

Type the Process Name into the Name and Display Names fields, as shown below (this name isspecified in the eai.cfgfile).

7

8



For the SiebelEAI_jcdUpsert project, perform this step for the following:

■ SeeBeyond HTTP Delete■ SeeBeyond HTTP Execute■ SeeBeyond HTTP Query■ SeeBeyond HTTP Update

In Object Explorer, go to Business Service > Business Service Method:

a. Type ProcessName into the Name field.

b. Type the actual Process Name into the Value field (see the figure below).

For SiebelEAI_jcdUpsert project, perform this step for:

■ SeeBeyond HTTP Delete■ SeeBeyond HTTP Execute■ SeeBeyond HTTP Query■ SeeBeyond HTTP Update

9



Creating a Subsystem for a Deployed WorkflowUse the following procedure to create a subsystem for a deployed workflow.

▼ To Create a Subsystem For a Deployed WorkflowLog in to Siebel Client 7.7, designating the appropriate Siebel server.

Click the Site Map in the Siebel Client home page.

Click the Administration - Server Configuration link. The Administration - Server Configurationpage appears.

FIGURE 1–9 Administration - Server Configuration

1

2

3

Creating a Subsystem for a Deployed Workflow


Click the Profile Configuration link.

In the Profile Configuration page, create the Named Subsystem (SEEBEYOND_HTTP_UPDATE).

Set the Workflow Process to Execute parameter for SEEBEYOND_HTTP_UPDATE to SeeBeyondHTTP Update.

Set the Service Method to Execute parameter for SEEBEYOND_HTTP_UPDATE to RunProcess.For this example, SEEBEYOND_HTTP_UPDATE is the name of the Named Subsystem.SeeBeyond HTTP Update is the Business Service that invokes the SeeBeyond HTTP UpdateWorkflow. .

FIGURE 1–10 Administration - Profile Configuration

4

5

6

7



FIGURE 1–11 SEEBEYOND_HTTP_UPDATE Named Subsystem



configuring siebel eai workflows

Documents