Siebel EFinance For Teller Connector To IBM WebSphere .

1y ago
101 Views
2 Downloads
1.24 MB
134 Pages
Last View : 6d ago
Last Download : 3m ago
Upload by : Brady Himes
Transcription

SIEBEL EFINANCE FOR TELLERCONNECTOR TO IBMWEBSPHERE BUSINESSCOMPONENT COMPOSER GUIDEVERSION 7.0, REV. H12-BCK98JAugust 2002

Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404Copyright 2002 Siebel Systems, Inc.All rights reserved.Printed in the United States of AmericaNo part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, includingbut not limited to photocopy, photographic, magnetic, or other record, without the prior agreement and writtenpermission of Siebel Systems, Inc.The full text search capabilities of Siebel eBusiness Applications include technology used under license fromFulcrum Technologies, Inc. and are the copyright of Fulcrum Technologies, Inc. and/or its licensors.Siebel, the Siebel logo, TrickleSync, TSQ, Universal Agent, and other Siebel product names referenced hereinare trademarks of Siebel Systems, Inc., and may be registered in certain jurisdictions.Other product names, designations, logos, and symbols may be trademarks or registered trademarks of theirrespective owners.U.S. GOVERNMENT RESTRICTED RIGHTS. Programs, Ancillary Programs and Documentation, deliveredsubject to the Department of Defense Federal Acquisition Regulation Supplement, are “commercial computersoftware” as set forth in DFARS 227.7202, Commercial Computer Software and Commercial Computer SoftwareDocumentation, and as such, any use, duplication and disclosure of the Programs, Ancillary Programs andDocumentation shall be subject to the restrictions contained in the applicable Siebel license agreement. Allother use, duplication and disclosure of the Programs, Ancillary Programs and Documentation by the U.S.Government shall be subject to the applicable Siebel license agreement and the restrictions contained insubsection (c) of FAR 52.227-19, Commercial Computer Software - Restricted Rights (June 1987), orFAR 52.227-14, Rights in Data—General, including Alternate III (June 1987), as applicable. Contractor/licensoris Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404.Proprietary InformationSiebel Systems, Inc. considers information included in this documentation andin Siebel eBusiness Applications Online Help to be Confidential Information.Your access to and use of this Confidential Information are subject to the termsand conditions of: (1) the applicable Siebel Systems software licenseagreement, which has been executed and with which you agree to comply; and(2) the proprietary and restricted rights notices included in this documentation.

ContentsIntroductionHow This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Additional Documentation. 8Using the Siebel Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Chapter 1. Overview: Siebel Teller MessagesSiebel Teller Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Required Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14IFX XML and Siebel Teller Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Teller XML Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Teller Domain Message Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Teller DTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Siebel Connector for Teller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 16Modifying a Siebel Connector for Teller . . . . . . . . . . . . . . . . . . . . . . . . 18Sample Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Chapter 2. Teller IFX XML ConnectorIFX XML Syntax and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21IFX XML Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Status Information and Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28FINS IFX XML Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29FINS IFX XML Dispatcher Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30IFX XML Transaction Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Version 7.0, Rev. HSiebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide3

ContentsTransaction Manager User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Transaction Manager Methods and Arguments . . . . . . . . . . . . . . . . . . . . . . 33FINS IFX XML Data Transformation Engine (DTE) . . . . . . . . . . . . . . . . . 37DTE Methods and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37FINS IFX XML Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Converter User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Converter Methods and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Outcalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50FINS IFX XML Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Dispatcher User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Dispatcher Methods and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Transport Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Teller IFX XML Workflow Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Low-Level Teller Connector Workflow Process Flow . . . . . . . . . . . . . . . . . . 82Chapter 3. Teller IFX Connector RoadmapIntegration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Configuring a Dispatcher Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Examining an Existing Dispatcher Map . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuring a Teller XML Integration Object Wizard . . . . . . . . . . . . . . . 92Examining an Existing Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Configuring the Envelope Integration Object . . . . . . . . . . . . . . . . . . . . . 95Configuring the External Integration Object . . . . . . . . . . . . . . . . . . . . . 96Examining an Existing External Integration Object . . . . . . . . . . . . . . . . . . . 96Configuring Internal Integration Object . . . . . . . . . . . . . . . . . . . . . . . . 100Creating New Internal Integration Objects Versus Reusing Existing InternalIntegration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Creating Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Preparation: Locking the Project and Creating the Dispatcher Map IntegrationObject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer GuideVersion 7.0, Rev. H

ContentsLocking the Project and Selecting the DTD File . . . . . . . . . . . . . . . . . . . . 102Creating External Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Creating New Internal Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . 105Compiling the Integration Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Configuring the Connector Components . . . . . . . . . . . . . . . . . . . . . . . .108About FINS IFX XML Transaction Manager . . . . . . . . . . . . . . . . . . . . . . . 109FINS IFX XML Data Transformation Engine . . . . . . . . . . . . . . . . . . . . . . . 110FINS IFX XML Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110FINS IFX XML Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Configuring the Data Transformation Maps . . . . . . . . . . . . . . . . . . . . . . 112Configuring the Workflow Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Adding a New Message to a Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Initiating Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Runtime Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Action Set Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Runtime Event Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Configuring Events in Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Enabling Runtime Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Runtime Event Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . 120Command Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Activating Workflow Seed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Activating DTE Seed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Activating Runtime Event Seed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Setting the Transport Manager URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Appendix A. Teller ObjectsMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Workflow Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Version 7.0, Rev. HSiebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide5

Contents6Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer GuideVersion 7.0, Rev. H

IntroductionThis book will be useful primarily to people whose title or job description matchesone of the following:Business Analysts Persons responsible for analyzing application integrationchallenges and planning integration solutions at an enterprise.Siebel FinancialServicesApplicationAdministratorsPersons responsible for planning, setting up, and maintainingSiebel Financial Services applications.Siebel FinancialServicesApplicationDevelopersPersons responsible for planning, implementing, and configuringSiebel Financial Services applications, and possibly adding newfunctionality.Siebel FinancialServicesIntegrationDevelopersPersons responsible for analyzing a business situation or using theanalysis of a business analyst to build the integration solution atan enterprise for Siebel Financial Services applications.Siebel SystemAdministratorsPersons responsible for the whole system, including installing,maintaining, and upgrading Siebel products.System Integrators Persons responsible for analyzing a business situation or using theanalysis of a business analyst to build the integration solution atan enterprise for specific applications, to develop customsolutions, or both.Also included in the audience for this book is any user with experience in dataintegration, data transformation (data mapping), scripting or programming, andXML.Version 7.0, Rev. HSiebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide7

IntroductionHow This Guide Is OrganizedHow This Guide Is OrganizedThis guide describes the Siebel Connector for Teller architecture as well as how toconfigure and use the Siebel Connector for Teller to integrate, share, and replicatedata between Siebel Financial Services applications and external applications.Following is a list of documentation for Siebel Financial Services eBusinessApplication Integration (eAI) and all the pre-built connectors. Siebel Financial Services eBusiness Application Integration Guide Siebel Financial Services Connector for ACORD P&C and Surety Guide Siebel Financial Services Connector for IFX XML GuideFor all other information about the Siebel Connector for Teller, refer to the DTD fileslocated in the FINS Tools installation directory: tools home directory \FINSEAI\TELLER\DTDV101.Additional ResourcesThe product documentation set for Siebel Financial Services applications isprovided on the Siebel Financial Services Bookshelf CD-ROM. For generalinformation about Siebel product documentation, see the Siebel Financial ServicesBookshelf Welcome page and Siebel Financial Services Documentation Roadmap.EAI-Associated Books. Review Overview: Siebel eBusiness Application IntegrationVolume I and Siebel Financial Services eBusiness Application Integration Guide tolearn what Siebel eAI is offering as a base product for Siebel Financial Services eAI.Refer to Tools Online Help if you plan on using COM, CORBA, or the ActiveX Plugins to accomplish integration. Tools Online Help serves as a reference for Siebelbusiness objects and components. Read both Siebel Tools Guide and Siebel WorkflowAdministration Guide to gain an understanding of the tools required for creatingintegrations. Read the Siebel Enterprise Integration Manager Administration Guideif you will perform bulk loading or unloading of data. The Connector books providespecifics on each of the associated connectors.Teller Domain Message Specification and Data Type Definition (DTD). The DTD files arelocated in the FINS Tools installation directory: tools homedirectory \FINSEAI\TELLER\DTDV101.8Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer GuideVersion 7.0, Rev. H

IntroductionUsing the Siebel ProductInteractive Financial Exchange (IFX) Specification. The Interactive Financial Exchange(IFX) Specification is managed by IFX Forum and is freely available atwww.ifxforum.org. It provides a framework for the exchange of financial data andinstructions independent of a particular network technology or computingplatform. The information-sharing potential of IFX has been designed to supportcommunication not only between a financial institution and its customers, but alsobetween a financial institution and its service providers, between financialinstitutions, and eventually directly between customers.For information on the XFS standard, go to www.xfsws.com.Using the Siebel ProductIt is strongly recommended that you read Fundamentals so that you can makeoptimal use of your Siebel application, especially if you are new to Siebel software.Fundamentals provides detailed coverage of the Siebel user interface and how touse it; working with data; locating information with the query and find features;sharing information with other users; and so on. The features presented inFundamentals appear throughout the Siebel application suite; they are introducedthrough procedures you can learn and use in your own Siebel application.Revision HistorySiebel eFinance for Teller Connector to IBM WebSphere Business ComponentComposer Guide, Version 7.0, Rev. HVersion 7.0, Rev. HSiebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide9

IntroductionRevision History10Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Overview: Siebel Teller Messages1This chapter describes Siebel Connector for Teller architecture and the requiredcomponents for the IFX connector. It also includes information about IFX-XML andSiebel Teller messages, as well as information about how to modify SiebelConnector for Teller.Version 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide11

Overview: Siebel Teller MessagesSiebel Teller ArchitectureSiebel Teller ArchitectureThe Siebel Connector for Teller extends the functionality of the Siebel Connector forIFX XML to provide Teller-specific data exchange between Siebel and other systems.A Siebel connector is a configured set of components that allow data to beexchanged between internal and external applications and databases. The Siebelsoftware uses XML (Extensible Markup Language) to format the data so that it canmove between systems with different data structures and be based on differentdatabase concepts.The Siebel Connector for Teller is a set of teller-specific XML business messages thatextend the capabilities of the Siebel Connector for IFX XML, as shown in Figure 1.Figure 1.12The Siebel Connector for Teller Extending the Siebel Connector for IFX XMLSiebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Overview: Siebel Teller MessagesSiebel Teller ArchitectureThe Siebel Connector for Teller extends the functionality of the Siebel Connector forIFX XML, but makes no change to the IFX XML architecture. Figure 2 displays thebasic connector architecture.Figure 2.Connector ArchitectureThe basic structure of the Siebel Connector for Teller is exactly the same as the basicstructure of the Siebel Connector for IFX XML. The methods and arguments used toconfigure the components are the same, with a few additional arguments for someof the methods. Use the IFX XML Wizard to create the necessary integration objectsfor the Siebel Connector for Teller.The main difference between the Siebel Connector for Teller and the SiebelConnector for IFX XML is that you will use the Teller DTD instead of the IFX DTDwhen creating integration objects.For information about the Siebel Connector for IFX XML, see Siebel FinancialServices Connector for IFX XML Guide. The remaining chapters in this documentassume that you have read and understood Siebel Financial Services Connector forIFX XML Guide.Version 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide13

Overview: Siebel Teller MessagesRequired ComponentsRequired ComponentsThe IFX connector requires the following components in order to implementmessage exchanges between Siebel applications and IFX-compliant applications: Siebel Financial Services application. A license to use the Siebel IFX Connector.The IFX connector license key can be obtained from Siebel ManufacturingOperations. Please ask your technical account manager to obtain your licensekey, or log a service request on Siebel SupportWeb.NOTE: Siebel Connector for IFX XML is not automatically available as part ofSiebel Financial Services, but must be purchased separately. Siebel Event Manager to initiate a workflow process through a Siebel workflowmanager (optional). In the absence of Event Manager, an eScript can initiate aworkflow process. Siebel Workflow is delivered as a part of Siebel FinancialServices.NOTE: You should also be familiar with IFX XML models. Additional informationabout these models can be obtained by visiting www.IFX.org.This document assumes that all these products have been successfully installed andtested for completeness by trained personnel before starting to use the IFXConnector for integration.14Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Overview: Siebel Teller MessagesIFX XML and Siebel Teller MessagesIFX XML and Siebel Teller MessagesIFX is a financial industry definition of XML. It contains messages appropriate forthe financial and banking industries. The Siebel Teller extension to the IFX XMLmessage set provides additional messages for use in exchanging information fromteller stations to non-Siebel databases.The Teller XML standard defines the required structure and format of an XMLmessage for use with an IFX converter. The definition exists in the Teller DTD, andthe Teller DTD incorporates the IFX DTD to construct messages.For a summary of the IFX XML syntax and rules, see Siebel Financial ServicesConnector for IFX XML Guide.Teller XML Message ExampleThe following is a sample Teller-XML document. ?xml version "1.0" encoding "UTF-8"? ?ifx version "1.0.1" oldfileuid "" newfileuid "" ? !DOCTYPE IFX SYSTEM "http://server/teller.dtd" IFX SignonRq SessKey 123-ABC2001-11-14T14:22:24.0-08:00 /SessKey ClientDt 2001-11-14T14:22:30.0-08:00 /ClientDt CustLangPref ENU /CustLangPref ClientApp Org ZKB /Org Name Siebel /Name Version 1.0 /Version /ClientApp /SignonRq tllr.TlrSvcRq SPName Legacy System /SPName RqUID 4E583573-ADA8-41c3-A002-CB70EE6D2BAB /RqUID tllr.BrnOpenRq RqUID 534572C9-4C9B-4f1e-A8DE-69F3C9AA8874 /RqUID tllr.BranchId BRANCH001 /tllr.BranchId /tllr.BrnOpenRq /tllr.TlrSvcRq /IFX Version 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide15

Overview: Siebel Teller MessagesIFX XML and Siebel Teller MessagesTeller Domain Message SpecificationThe Teller message specification is an extension to the standard IFX XMLspecification. It is delivered as a separate DTD file that includes the IFX DTD. It waswritten based on IFX version 1.0.1. Both the Teller and IFX DTD files are located inthe FINS Tools installation directory: tools home directory \FINSEAI\TELLER\DTDV101.Teller DTDUse the Teller DTD with the IFX XML wizard to create an appropriate set ofintegration objects and properly update the Dispatcher Map.Select the Teller DTD (teller.dtd) when using the IFX XML wizard to create a SiebelConnector for Teller.Siebel Connector for Teller ConfigurationA Siebel Connector for Teller consists of a combination of the Siebel technologiesshown in Table 1.Table 1.16Siebel Connector for Teller TechnologiesComponentRoleRuntime EventsTriggers the connector workflow.Command ObjectsTriggers the connector workflow.Workflow ProcessesControls the flow of data between Siebel and the externalsystem. Calls the various business services to perform theirtasks.Integration ObjectsStores data from Siebel (as internal integration objects) or fromthe XML message (as external integration objects).Business ServicesPerform various tasks to handle the transformation of datafrom Siebel to external system and back.Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Overview: Siebel Teller MessagesIFX XML and Siebel Teller MessagesTable 2 displays a list of the major business services and their functions. Thecomplete details of the business services are described in Chapter 2, “Teller IFXXML Connector.”Table 2.Business ServicesBusiness ServiceFunctionFINS IFX XMLTransaction ManagerCall a predefined business service (usually the Siebel Adapter)to extract data from Siebel and to update data in Siebel.FINS IFX XML DTETransform integration objects from internal format to externalformat, and vice versa.FINS IFX XML ConverterManage the IFX session key and transform date formats.FINS IFX XMLDispatcherHandle incoming messages by identifying the body and headersections.Version 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide17

Overview: Siebel Teller MessagesModifying a Siebel Connector for TellerModifying a Siebel Connector for TellerIn general, you will not need to create a Siebel Connector for Teller from scratch.This section describes how to modify the existing connector infrastructure toaccommodate new and modified messages.For an example of creating a connector, see “Configuration Roadmap” in SiebelFinancial Services Connector for IFX XML Guide.To add a new message to a Siebel Connector for Teller1 Run the IFX XML wizard to create internal and external integration objects.The external integration object is based on the DTD. Be sure to choose theteller.dtd file.The internal integration object is based on the business component.2 Create a data transformation engine (DTE) map to map the integration objectfields to each other.3 Build a workflow or modify an existing one to handle the new message.4 Add a button or event to an applet to trigger the workflow.5 Test the workflow.Sample WorkflowTable 3 presents a sample workflow for a Siebel Connector for Teller.Table 3.18Sample WorkflowWorkflowDescriptionFINS Teller Session ConnectorManages all Teller transaction messages from theTeller Session business component.Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Teller IFX XML Connector2This chapter describes the methods, input arguments, and output arguments forconfiguring the components of a Siebel Connector for IFX XML.The Siebel Connector for IFX XML consists of the following components: Transaction Manager Transformation Engine Converter Dispatcher Transport AdapterFigure 3 shows the connector components.Figure 3.Siebel Connector for IFX XML ComponentsVersion 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide19

Teller IFX XML ConnectorThe Connector components are Siebel business services, which are configured inthe Workflow view. The integration objects are created using the FINS IFX XMLwizard, and they are configured using the Data Map editor.NOTE: For information about Siebel integration objects, converter elements, andXML, see XML Integration Reference.20Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Teller IFX XML ConnectorIFX XML Syntax and RulesIFX XML Syntax and RulesIFX is a financial-industry version of XML. It contains messages that are appropriatefor the financial and banking industries.The IFX standard defines the required structure and format of an XML message foruse with a Siebel connector. The definition is in the IFX DTD, and the IFX DTD isincorporated by the Siebel Connector to construct messages.This section provides a summary of the IFX XML syntax and rules, and provides theappropriate vocabulary for discussing IFX XML messages. This section suppliesknowledge that is basic for any troubleshooting you may need to do.IFX XML DocumentsEach IFX XML document has three distinct parts: Envelope Header BodyThe parts are presented as a hierarchy. The envelope is the root, which contains theheader and the body. Elements of an IFX XML document that contain otherelements are called aggregates.The envelope and header provide information required by the XML converter andby other components in the connector. The services identify the kind of businessservice affected by the information, and the messages provide the data that is beingexchanged. There are elements that precede the message proper, which specify theversions of XML and IFX.Sample IFX XML Document ?xml version "1.0" encoding "UTF-8" ? ?ifx version "1.0.1" oldfileuid "00000000-0000-0000-0000000000000000" newfileuid "11111111-1111-1111-1111-111111111111"? IFX SignonRq SessKey ABCDEFGHIJKLMNOPQRSTUVWXYZYXWVUTSRQPONML /Version 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide21

Teller IFX XML ConnectorIFX XML Syntax and RulesSessKey ClientDt 2001-10-10T17:04:33.0-07:00 /ClientDt CustLangPref ENU /CustLangPref ClientApp Org Customer Organization /Org Name Siebel FINS /Name Version 7.0 /Version /ClientApp /SignonRq PaySvcRq SPName IFX Service Provider /SPName RqUID 7796AAAA-685E-47b0-9C2F-27FB475B05FA /RqUID PmtAddRq RqUID 83DA5F9C-7781-4ebb-BB62-311B8B9C6AD7 /RqUID PmtInfo RemitInfo CustPayeeId SibelCustomerBank /CustPayeeId CurAmt Amt 500 /Amt CurCode US /CurCode /CurAmt /RemitInfo DepAcctIdFrom AcctId 2547-86392 /AcctId AcctType CDA /AcctType BankInfo Name SiebelCustomerBank /Name /BankInfo /DepAcctIdFrom DueDt 2001-12-24 /DueDt /PmtInfo DupChkOverride 1 /DupChkOverride /PmtAddRq /PaySvcRq /IFX EnvelopeThe envelope is the root element of an XML document. For an IFX XML document,it begins with IFX and ends with /IFX .The indicator IFX is the only item in the envelope.22Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H

Teller IFX XML ConnectorIFX XML Syntax and RulesHeaderEvery message header has a sign-on element that authenticates the message, and itmay have a sign-off element that ends a particular session.The header has four terms: SignonRq SignonRs SignoffRq SignoffRsThe header for a request has the header element SignonRq . The header for theresponse has the header element SignonRs . Similarly, the sign-off elements arespecifically for requests and responses.NOTE: IFX XML messages must be either requests or responses. Requests andresponses cannot be mixed in a single message. A request uses SignonRq . Aresponse uses SignonRs . Signon InformationThe SignonRq or SignonRs header element provides a location for statusinformation, authentication information, date and time stamps, languagepreferences, and identification of the application that will use the data. You can findcomplete information in the IFX specification.Authentication InformationThe initial SignonRq for any session must provide authentication information,typically the user name and password or a certificate ID. When the serverauthenticates the user, using the information in the header, the server issues asession key in the SignonRs . Subsequent messages use the session key as atoken. After a session has finished, any subsequent session must start with theauthentication information again.Version 7.0, Rev. H Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide23

Teller IFX XML ConnectorIFX XML Syntax and RulesThe following is an example of an initial SignonRs authentication element. SignonRq SignonPswd

12 Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide Version 7.0, Rev. H Siebel Teller Architecture The Siebel Connector for Teller extends the functionality of the Siebel Connector for IFX XML to provide Teller-specific data exchange between Siebel and other systems.

Related Documents:

Downloading and Installing the Siebel Mobile Application Container (Siebel App). 4-20 Using the Siebel Mobile Archive MAA File (Administrator Task) . 4-21 Setting Up the Host Server for Siebel Mobile . 4-21 Configuring the Siebel Mobile Application Container (Siebel App) on an iOS Device . 4-22 Clearing the Application Cache for .

Siebel CRM Pricing Prices in USA-Dollar (USD) License Price Software Update License & Support Licensing Metric Minimum Siebel CRM General Siebel Advanced Market Development Funds 500 110.00 Application User Siebel Anywhere 200 44.00 Application User Siebel Server Sync - Microsoft Exchange Server 120 26.00 Application User Siebel Content Publishing 120

How Siebel CRM Desktop Handles a Microsoft Outlook Task 56 How Siebel CRM Desktop Handles a Microsoft Outlook Email Message 56 How Siebel CRM Desktop Handles Items If the User Removes the Siebel CRM Desktop Add-In 57 How a User Can Link a Siebel CRM Record to a Microsoft Outlook Record 58 Chapter 5: How Siebel CRM Desktop Synchronizes Data

Thomas M. Siebel . Aspenia. 79. 2018. Thomas M. Siebel is Chairman and CEO of C3 IoT. He previously founded Siebel Systems and the Thomas and Stacey Siebel Foundation, which cre ated the Siebel Energy Institute in 2015. 097-108 Siebel-ing 79 SCENARIO.indd 98 11/06/18 15.01

The Siebel Mobile Connector allows partners and customers to create voice, wireless, and other applications with Siebel Business content. The Siebel Mobile Connector is a standards-based API that delivers well-formed XML from an optimized Siebel File Size: 931KBPage Count: 168

- PowerCenter 7 (Informatica etl august 2005) Siebel : - Siebel Datawarehouse developer (june 2005) - Siebel EIM Workshop (23rd june 2003) - Siebel 7 EAI (October 2002) - Siebel 7 Core Consultant (April 2002) - Siebel 2000 EAI (march 20

Siebel Performance Tuning Guide Version 8.0 3 Contents Siebel Performance Tuning Guide 1 Chapter 1: What's New in This Release Chapter 2: Siebel Architecture and Infrastructure About Performance and Scalability 13 About Siebel Architecture and Infrastructure 14 About Siebel User Request Flow 18 Performance Tuning Terminology 19

Available for a number of programming languages. Reference implementation in PythonbyVladimir Keleshev. No longer necessary to write much code only: import docopt args docopt.docopt(_doc_, version _version_) The rest is documentation (and the code for actually using the command-line arguments) Finn Arup Nielsen 10 July 4, 2014. Python scripting Docopt example #!/usr/bin/env python .