|Bookshelf Home | Contents | Index | PDF|
The code generated for a business service includes a class representing the business service itself as well as classes representing inputs and outputs of its methods. These classes are described in detail in this section.
ASI business services based on the data sync service have integration objects as part of the input or output of their methods. The JavaBeans representing these integration objects must be generated separately from the business service.
Depending on whether the beans are based on the Java Data Bean or the Siebel JCA Resource Adapter. For example, generated JDB code for the EAI Siebel Adapter resides in the package com.siebel.service.jdb.eaisiebeladapter.
The Code Generator creates the standard Java directory structure reflecting the package structure. As shown in Figure 3, a subfolder named com is created in the folder specified during the generation process. Below the com folder is a folder named siebel containing a folder named service, containing a folder named jdb (or jca), containing a folder named for the business service. This last folder contains the classes for the business service. Each class is defined in its own file.
One Java class is generated to represent the business service itself. The name of the class is the name of the business service with all special characters replaced by underscores (_) and BusServAdapter appended to the end. For example, the class representing EAI Siebel Adapter is EAI_Siebel_AdapterBusServAdapter.
The Java class has one method for each method of the business service. Its name is the name of the method with m prepended. For code based on the Java Data Bean, the class is a subclass of com.siebel.integration.adapter.SiebelJDBAdapterBase. For code based on the Siebel Resource Adapter, the class is a subclass of com.siebel.integration.adapter.SiebelJCAAdapterBase.
Additionally, for each method of the business service defined in Siebel Tools, one Java class is created for the method's input and one for the method's output. The name of the class is the name of the method with Input or Output appended. The class encapsulates all input (or output) arguments for the method. Each argument is represented as a field whose name is that of the argument with f prepended. For each field, public set and get methods are provided Java methods for reading and writing their values.
The first class, CC_XML_Converter BusServiceAdapter, represents the business service as a whole; it has methods mPropSetToXML and mXMLToPropSet. The other three classes represent the input or output parameters of the two methods. (Notice there is no class XMLToPropSetOutput because that method has no outputs.) Those three classes each have methods to read and write the individual parameters, as well as methods to convert to and from a com.siebel.data.SiebelPropertySet.
|Transports and Interfaces: Siebel Enterprise Application Integration||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|