Bookshelf v7.5: Examining an Existing Wizard

Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide > Teller IFX Connector Roadmap > Configuring a Teller XML Integration Object Wizard >

Examining an Existing Wizard

To learn more about using the Teller XML Integration Object wizard, open and study one in Siebel Tools. A good wizard to study for this purpose is the FINS Teller Integration Branch Wizard. Examine the user properties of the business service.

Table 39 shows the presetup user properties for the FINS Teller Integration Branch Wizard.

Table 39. User Properties for the FINS Teller Integration Branch Wizard
Name	Value	Description
DispatcherMapName	FINSTlrBranchDispMap	The Dispatch Map Name wizard will use this map to update the key and value.
HasUIControl	True	Internal use.
Integration Object Wizard	Y	Internal use.
Integration Object Base Object Type	Siebel Business Object	Internal use.
Operation KeyWord Match:0	Add/IXMLOperation_ADD	Internal use. This means that when the wizard generates an external integration object for a message with the word Add in it, it creates a dispatcher map entry with the action of IXMLOperation_Add. This entry should match a user property on the FINS IFX XML Transaction Manager. This user property identifies a business service and method to run when the response message received is an "Add" message. The operation is defined in the Transaction Manager as "SAUpsert." The operation name will be recorded in the dispatch map.
Default Envelope Tag	IFX	Value for the Envelope Tag.

You can customize the Teller XML Integration Object Wizards to fit your needs or create new ones under certain conditions.

In the following situations, customize the available wizard:

When you need to use a Dispatcher Map other than the one provided.

When you need to use different Siebel operations for the same type of messages.

In the following situations, create a new wizard:

When you need to work in parallel and you want your integration objects to be created in different Tools projects. (All integration objects are created in the same Tools project that the Wizard business service is in.) To do this, copy the Wizard business service to the new project and rename it.

When the same message needs to be sent from events that are based on different internal integration objects, which means you need the same message entry in different Dispatcher maps. To do this, you could manually adjust the dispatcher map instead of creating a new Wizard business service.

Once you have customized the existing wizard or created a new wizard, compile the definition into the repository that Siebel Tools is using before the changes take effect.

NOTE: The repository Siebel Tools is using is different from the repository SRF file the application uses.