Upgrading and Migrating Siebel Janna Applications > Interoperability >

Integrating the User Interface

A second potential approach is to implement User Interface (UI) Integration. It is similar to Data Integration in that the data comes from a Siebel Janna database using a distributed environment. Unlike the Data Integration approach, however, the Siebel Applet can be associated with either a VBC or a standard Siebel Business Component. At the presentation layer, the Applet acts as a host to the corresponding ASP page for the Siebel Janna zone. In effect, the Applet serves as a container for the ASP page, so the User Interface looks essentially as it does in the Siebel Janna application. For more information about VBCs and the Siebel Janna Gateway Business Service, see Integrating Data.

NOTE:  Before you begin configuring your Siebel application for UI integration with Siebel Janna, please make sure your environment is configured correctly with a functioning Siebel Janna Web Client application and Siebel eBusiness application.

To configure Siebel for UI Integration with Siebel Janna, you must perform the following tasks:

• Identify the Siebel Janna Web Client Zone that will be hosted in Siebel.
• Create the applet component definition in Siebel Tools.
• Set the applet user properties in Siebel Tools.
• Add the applet to the appropriate view.
• Compile the applet and view.

To configure Siebel for integration with Janna

1. Identify the Siebel Janna Web Client Zone.
   1. Determine the Siebel Janna Web Client ASP Path for a particular Siebel Janna Zone by referring to the development documentation. You may also check the Siebel Janna Web Client JASPLink table and other associated configuration tables. The Siebel Janna Web Client Zone ASP path is found in the JASPLink table in the ASPFile column.
   2. Determine the ASP parameters required by the Siebel Janna Zone you wish to display in a Siebel View. The ASP parameter values are dependent upon individual Zone implementation. The best source for this information is the technical design and development documentation of the Zone. If this is unavailable, then the implementation should be reviewed by engineering or other technical resources to determine the correct ASP Parameter values.
2. Create the applet component definition in Siebel Tools.
   1. Locate the Siebel Janna Zone Adapter Applet in the Applet Object Types in Siebel Tools.
   2. Make a copy of this record by right-clicking on its row indicator and clicking Copy.
   3. Enter an appropriate name for the new applet row.
   4. Select the appropriate Project for your applet component.
3. Set the applet user properties in Siebel Tools.
   1. Using the information from Step 1, configure the ZoneSRC property of the new applet. Configure the Property as follows:

   http:\\<server>\webview\ie\<zone ASP file Name>

   2. Using the information from Step 1, configure the ASPParams User Property with a semicolon-delimited list of the Fields from the Business Components whose values will be passed to the Request variables collection of the ASP Zone. The User Property has the following format:

   <BusComp Field1>;<BusComp Field2>;...;<BusComp Fieldn>

4. Add the applet to the appropriate view using Siebel Tools, just as you would any other Siebel Applet.
5. Compile the applet and view.

For a list of definitions of the terms mentioned in the preceding sections, please see Siebel Janna Terminology and Architecture.

Siebel Janna Adapter Requirements

A Siebel Janna adapter would be a predefined business service that would function similar to the SAP BAPI Adapter. This adapter can be used as part of a workflow to send and receive information to Siebel Janna applications. The following are the requirements for enabling this business service.

• The business service should be a prebuilt business service similar to other eAI adapters like the SAP BAPI adapter.
• The business service should have one method: Execute.
• The method arguments for this business service should be as follows:
  • Integration Object Instance (the external integration object corresponding to the Siebel Janna service object)
  • Connect String
  • Username
  • Password
  • Output Integration Object (in case a response is received)

The Siebel Janna Service Objects in Siebel Janna applications can be represented as external integration objects. The requirement for the Integration Object Wizard to support Siebel Janna service objects is as follows:

• The Integration Object Wizard needs to support an additional object type called the Siebel Janna Service Objects.
• In Siebel Janna Tools this wizard will have the ability to read the metadata from Siebel Janna on these Siebel Janna Service Objects and create an external integration object corresponding to the Siebel Janna Service Objects.
• The object must work with both the 2000 and 2001 suites.

Siebel Janna Gateway Requirements

A Siebel Janna Gateway Business Service would interact with VBCs in Siebel and the Siebel Janna Service Objects in Siebel Janna to exchange information between the two systems. A Siebel Janna Gateway is similar to the XML gateway that currently exists.

To get to the Siebel Janna data, the Gateway Business Service calls the appropriate Siebel Janna Service Object. The Siebel Janna Service Object is responsible for performing actions on behalf of the client (Siebel). When Siebel requests that data be fetched from the Siebel Janna application, the results of the fetch come back in the form of a Siebel Janna Data Object.

The Siebel Janna Gateway Business Service must support the following methods:

• Delete
• Insert
• Init
• PreInsert
• Query
• Update

This business service takes the following information as parameters:

Service Object name

The parameter is specified when configuring the VBC and part of the Business Component user property. The format should be as follows:

Service Name = Siebel Janna Gateway

Service Parameters = "ServiceObjectName=<Siebel Janna Service Object Name>"