Oracle® Application Server Adapter for Siebel User's Guide 10g Release 2 (10.1.2) B14062-03 |
|
Previous |
Next |
This chapter contains examples of service and event integration with Siebel.
The scenarios shown in this chapter require the following prerequisites.
Prerequisites
OracleAS Adapter for Siebel must be installed on Oracle Application Server.
Oracle BPEL PM Server must be properly configured and running.
Oracle JDeveloper must be properly installed.
The examples in this chapter present the configuration steps necessary for demonstrating service and event integration with Siebel. Prior to using this material, you must be familiar with the following:
How to create a J2CA configuration, as BPEL PM is only compatible with the J2CA Connector. See "Creating a Configuration for J2CA" for more information.
How to configure OracleAS Adapter for Siebel for services and events using Application Explorer. See Chapter 2, "Configuring Oracle Application Server Adapter for Siebel" for more information.
How to use Siebel workflows. See Appendix A, "Using Siebel Workflows" for information on Siebel design requirements.
See Also: Oracle BPEL Process Manager Developer's Guide |
Adapter integration with Oracle BPEL Process Manager is a two-step process:
Design Time: OracleAS Adapter for Siebel is configured in Application Explorer for services and events, as described in Chapter 2, "Configuring Oracle Application Server Adapter for Siebel". Integration logic is modeled using JDeveloper.
Runtime: After you deploy the BPEL process you designed in JDeveloper, you can test your service configuration or see newly received events in the BPEL Console.
The following example describes how to add an IO node for Siebel.
Creating an Integration Object Node
Start Application Explorer.
Perform the following steps:
The defined Siebel targets are displayed under the adapter node.
Click the target name, for example, siebel, under the Siebel node.
Verify your connection parameters. Provide the required password.
Right-click the target name and select Connect.
The x icon disappears, indicating that the node is connected.
Expand the Integration Object node and select Sample Account.
Right-click the Sample Account node and select Add IO Node.
The following dialog box is displayed.
Enter a node name, for example SampleAccount in the Node name field and a path to the Sample Account XDR file in the Schema location field.
Please note:
For Siebel 7.5 or later: Generate XSD schemas directly from Siebel tools. You use the XSD schemas when you create Web services in Application Explorer. After you generate an XSD schema through Siebel tools, use it to create an IO node and a Web service.
For Siebel 7.0: You cannot generate XSD schemas directly from Siebel tools; only XDR schemas can be created. Before you create a Web service, you must first generate an XSD schema from the XDR schema using Application Explorer.
If the XSD schema has already been generated, select XSD Schema. If you are using Siebel-generated XDR schemas, do not select the XSD schema option.
Select a protocol from the Protocol list.
This topic illustrates Siebel service integration. It describes design-time and runtime configuration.
Before you design a process for Siebel service integration, you must create an outbound J2CA service (WSDL) using Application Explorer.
Creating a Request-Response J2CA Service in Application Explorer
To generate WSDL in Application Explorer:
Start Application Explorer and connect to a defined Siebel target or create a new target.
See Connecting to a Defined Target for more information.
Expand the Siebel target to which you are connected.
Expand Business Object, Account, Account. Navigate to queryWithView and right-click the object.
The following menu is displayed.
Select Create Outbound JCA Service (Request/Response).
The Export WSDL dialog box is displayed.
Accept the default name and location for the file.
The .wsdl file extension is added automatically.
Click OK.
Creating a BPEL PM Server Connection
Before you design a BPEL process, you must create a connection to your BPEL Server using JDeveloper. To create a server connection:
Open JDeveloper.
To display the connections, click the Connections tab at the bottom of the upper left pane in JDeveloper.
The following menu is displayed.
Right-click BPEL Process Manager Server and select New BPEL Process Manager Connection.
The Create BPEL Process Manager Connection - Welcome dialog box is displayed.
Click Next.
The Create BPEL Process Manager Connection dialog box is displayed.
Specify a unique name for your BPEL Server connection and click Next.
Specify a valid host name and port number for the BPEL PM Server you wish to connect to.
Your newly created server connection is displayed in the Connections tab under the BPEL Process Manager Server node.
Creating a BPEL Project for a Synchronous BPEL Process
To create a BPEL Project for a synchronous BPEL process:
At the bottom of the upper left pane, click the Applications tab and select a workspace for your project.
Right-click the workspace and select New Project.
The New Gallery window is displayed.
From the Items list, select BPEL Process Project and click OK.
The BPEL Process Project dialog box is displayed.
Perform the following steps:
Specify a name for the BPEL process.
The Namespace field is updated automatically.
From the Template list, select Synchronous BPEL Process.
Designing the BPEL Process for the queryWithView Outbound Service
From the Process Activities pane on the right, drag and drop a PartnerLink to the visual editor.
The Create Partner Link dialog box is displayed.
Click the WSIL browser icon (second icon from the left preceding the WSDL File field).
The WSDL Chooser dialog box is displayed.
Expand your new server connection, then expand adapters, and then applications.
Select queryWithView_invoke.wsdl and click OK.
The WSDL File field in the Create Partner Link dialog box displays the name and location of the selected WSDL file. The Partner Link Type field specifies the PartnerLink defined in the WSDL file.
Perform the following steps:
Leave the My Role field unspecified. The role of the PartnerLink is null, as it will be synchronously invoked from the BPEL process.
From the Partner Role list, select the default value queryWithViewRole. This is the role of the BPEL process.
Click OK.
Select Save from the File menu.
From the Process Activities pane on the right, drag an Invoke activity to the visual editor and place it between the Receive activity (receiveInput
) and the Reply activity (replyOutput
).
The Invoke process activity is shown in the following diagram view.
Drag the blue arrow from Invoke_1 and connect it to the Siebel PartnerLink.
The Edit Invoke dialog box is displayed.
Perform the following steps:
Click the first icon to the right of the Input Variable field, then click OK in the Create Variable window that is displayed.
Repeat the previous step to create a default variable for Output Variable.
Click OK.
Drag an Assign process activity and drop it between the receiveInput
Receive activity and Invoke_1
Invoke activity.
The following image shows the new Assign activity in JDeveloper visual editor.
Double-click the Assign activity icon.
The Assign dialog box is displayed.
In the Copy Rules tab, click Create.
The Create Copy Rule dialog box is displayed. Perform the following steps:
In the From pane, expand Variables, then inputVariable, and then highlight payload.
In the To pane, expand Variables, then Invoke_1_queryWithView_InputVariable, and then highlight input_queryWithView.
Your Create Copy Rule dialog box should look as follows:
To close the Create Copy Rule dialog box and the Assign dialog box, click OK.
From the Process Activities pane on the right, drag another Assign activity to the visual editor and place it between the Invoke activity (Invoke_1
) and the Reply activity (replyOutput
).
Double-click the Assign activity icon and click Create.
In the Create Copy Rule dialog box, map Invoke_1_queryWithView_OutputVariable, output_queryWithView to outputVariable, payload.
Verify that you have mapped all variables as follows:
Click OK, then click OK again.
Select Save from the File menu.
You have completed the design of your BPEL process.
Deploying the BPEL Process for the queryWithView Outbound Service
JDeveloper deploys BPEL processes directly to Oracle BPEL Console.
To deploy your BPEL process in JDeveloper:
Right-click your process flow in the Applications - Navigator pane.
Select Deploy, then Your BPEL PM Server connection, and then Deploy to default domain.
The Password Prompt dialog box is displayed.
Enter your BPEL Process Manager password in the Password Prompt dialog box.
The deployment process starts automatically after you enter the correct password.
Observe the Messages log at the bottom of the window.
The Messages log displays the deployment status. In this example, it shows a successful deployment message for the process.
If deployment was not successful, click the Compiler tab to view all error and warning messages generated during the deployment process.
To invoke the queryWithView process from Oracle BPEL Console:
Start Oracle BPEL Console by entering the following URL in a browser:
http://host:port/BPELConsole
Select a domain and provide a valid password.
The Oracle BPEL Console main page is displayed.
The BPEL Processes tab is displayed.
Click the Initiate tab.
The Initiate tab enables you to test your BPEL process.
Perform the following steps:
From the Initiating a test instance list, select XML Source.
Enter the following code in the text area provided for XML input:
<?xml version="1.0" encoding="UTF-8"?> <Siebel location="S/BO/Account/Account/queryWithView" view="AllView"> <select> <Name>SIEBEL*</Name> </select> <field>Name</field> <field>Location</field> </Siebel>
Click Post XML Message.
The response received from the Siebel system is displayed in the Initiate window.
This topic illustrates Siebel event integration. It describes design-time and runtime configuration.
Creating a Channel
You must create a separate channel for every inbound J2CA service and select that channel when you generate WSDL for inbound interaction using Application Explorer.
Note: If two or more events share the same channel, event messages may not be delivered to the right BPEL process. |
In the left pane, click Events.
Expand the Siebel node.
The ports and channels nodes appear in the left pane.
Right-click Channels and select Add Channel.
The Add Channel dialog box is displayed.
Perform the following steps:
Click Next.
The Basic dialog box is displayed.
Click OK.
The channel appears under the channels node in the left pane. An X over the icon indicates that the channel is currently disconnected.
Generating WSDL for Event Notification
After you create a channel and verify that it is not started, you must generate WSDL for the event using Application Explorer.
You must be connected to a Siebel target under the Adapters node in Application Explorer. See "Establishing a Connection (Target) for Siebel" for detailed information on how to define and connect to a target.
After you connect to a Siebel target, generate WSDL for the event as follows:
Expand the Integration Object node under the target and scroll down to SampleAccount.
Right-click SampleAccount.
Select Create Inbound JCA Service (Event).
The Export WSDL dialog box is displayed.
Perform the following steps:
In the WSDL File Name field, specify a name and location of the WSDL file.
In the Channel field, select the channel you created for this inbound service.
Important: You must create a separate channel for every inbound service. Verify that the channel is stopped before runtime.
If you are using the optional port feature, you must select a port from the Port list. See "J2CA Filtering Port Option for Integration with BPEL Process Manager" for more information.
If you are not using event ports for schema validation, skip this step. In this case, the default value of no port is selected automatically.
Creating a BPEL PM Server Connection
Before you design a BPEL process, you must create a connection to your BPEL Server using JDeveloper. See "Creating a BPEL PM Server Connection" for details on how to create the connection.
Designing the BPEL Process for the Inbound Service
To design a BPEL process for inbound interaction:
Click the Applications tab and select a workspace for your project.
Right-click the workspace and select New Project.
The New Gallery dialog box is displayed.
From the Items list, select BPEL Process Project and click OK.
The BPEL Process Project dialog box is displayed.
Perform the following steps:
Specify a name for the process, for example, Siebel_Event.
The Namespace field is updated automatically.
From the Template list, select Empty BPEL Process.
Click OK.
From the Process Activities pane on the right, drag and drop a PartnerLink to the visual editor.
The Create Partner Link dialog box is displayed.
Click the WSIL browser icon (second icon from the left preceding the WSDL File field).
The WSDL Chooser dialog box is displayed.
Expand your BPEL Server connection, then expand adapters, and then applications.
The WSDL Chooser dialog box is displayed.
Select SampleAccount.wsdl and click OK.
The Create Partner Link dialog box is displayed.
The WSDL File field displays the name and location of the selected WSDL file. The Partner Link Type field specifies the PartnerLink defined in the WSDL file.
Perform the following steps:
From the My Role list, select the default value TestRole.
Leave the Partner Role field unspecified.
Click Apply, and then OK.
The new Siebel_PL PartnerLink appears in the visual editor.
From the Process Activities pane on the right, drag a Receive activity to the visual editor and place it in the designated placeholder labeled Drop Activity Here.
Connect the Receive activity to the Siebel_PL PartnerLink.
The Edit Receive dialog box is displayed.
Perform the following steps:
Click Apply.
The Edit Receive dialog box should no longer display any warnings or errors.
Click OK.
Select Save from the File menu.
The completed inbound BPEL process looks as follows:
Deploying the BPEL Process for the Inbound Service
Perform the following steps:
Right-click your process flow in the Applications - Navigator pane.
Select Deploy, then Your BPEL PM Server connection, and then Deploy to default domain.
When prompted, enter your BPEL Process Manager password and click OK.
The deployment process starts automatically after you enter the correct password.
Observe the Messages tab at the bottom of the JDeveloper screen.
The following image shows successful deployment.
The following topic describes how to trigger an event in Siebel and verify event integration using OracleAS Adapter for Siebel.
Triggering a Siebel Event to Test Event Runtime Integration
To trigger an event in Siebel:
Start the Siebel Call Center by entering the following URL in a browser:
http://hostname/callcenter/start.swe
Click View and select Site Map from the list.
The Site Map view is displayed.
Click Siebel Workflow Administration.
The Siebel Workflow Administration page is displayed.
Click Workflow Processes.
The Workflow Processes page is displayed.
Click Query to search for the Workflow needed to trigger a Siebel event.
Enter a Siebel workflow name and click Search.
Select the workflow.
Click the Process Designer tab and double-click the Send Siebel Quote Data HTTP workflow element.
The Input Arguments tab is displayed.
Enter the IP address and port for the HTTPRequestURLTemplate input argument.
Click Return To Designer.
Click the Process Simulator tab.
The Simulator tab is displayed.
Click Start then Continue to complete the Siebel event triggering process.
Verifying the Results
To verify your results:
Log in to Oracle BPEL Console at
http://host:port/BPELConsole
Enter the password for your BPEL domain.
The default password is bpel
.
Click the Instances tab.
Recently received runtime events are displayed in the Instances tab.
Click the Siebel instance, then click Audit to see the event message.
The message received from the Siebel system is displayed in the Audit tab.