Bookshelf Home | Contents | Index | Search | PDF |
Upgrading and Migrating Siebel Janna Applications > Interoperability Case Study > Transaction Zone—Implementation Details >
Determining the ProgID of Siebel Janna Service Object
Depending on the kind of Siebel Janna Service Object (Core Service Object, Extension Service Object, Client Extension Service Object) there are several ways to determine the correct ProgID.
- For core Siebel Janna Service Objects, consulting the Siebel Janna Tools documentation should provide the correct ProgID for the Siebel Janna Data Object being integrated.
- For extension Siebel Janna Service Objects, consulting the technical design documents of the Extension implementation should contain the ProgIDs for Service Objects that were part of the Extension module.
- For client extension Siebel Janna Service Objects, the client technical design documents should contain the ProgIDs for Siebel Janna Service Objects that were part of the Client Implementation.
In the absence of accurate documentation, there are a number of tools that will allow a user to determine ProgID based on the compiled DLL (regedit or OLEView) that implements a DLL. If a compiled DLL is not available, use the source code of the Siebel Janna Service Object Implementation to determine its ProgID. Most often, Siebel Janna Service Object ProgIDs are formed from the SQL Table Name that the Siebel Janna Service Object maintains and take the following form:
<Module Name>.<SQL Table or View Name>.1
where <Module Name> is often <SQL Table or View Name> with SO appended to it. For Example, a Siebel Janna Service Object that maintains the SQL View vSomeViewData would have a ProgID of vSomeViewDataSO.vSomeViewData.1.
Bookshelf Home | Contents | Index | Search | PDF |
Upgrading and Migrating Siebel Janna Applications Published: 18 April 2003 |