Top
| home / infca / sk (navigation links) | Character determines fate |
| Curs | ICS | HH | Hints | Links | End |
The product family is WS Adapters
The new JCA Adapters are named WS Adapter for xxx v6.0
The WBI Adapters will renamin WS Bussiness Integration Adapters until withdrawn.
Tied to PS.
Tied to MB. Only MQ JMS libraries required. Creates (only) the Bussiness Objects for you, no Import, no Export. Adapter = JAR file => own JVM, no WAS. Es pot posar on calgui, a prop o lluny de la aplicacio, i parla amb el MB via MQ.
Visual Test Conector = simulates the Application, as SAP, for a quick demo !
No migration path (yet) from WBI Adapters to JCA Adapters.
[1] el del ICS s'escull a :
[2] el dels Conectors s'escull a :
Els missatges que venen de VExIxA no tenen el tag anomenat DOCTYPE i el identificador del missatge s'agafa d'un camp de dins de les dades del missatge. A aquest identificador s'afegeix el prefix HITIS_ En teoria segons diu la documentacio dels adaptadors, per fer aixo, s'ha de programar una clase de java dins del package anomenat CwCustDataHandler.
The Idoc-Control is defined inside the business object
as first folder :
element Name = Control_record and Type = sap_idoccontrol
If you need of that as single business object,
you can find it in the Business Objects folder
To display it, you can double-click on it,
and you can see its elements with the Business Object Designer.
Lookup the adapter specific documentation talking about "Meta-objects configuration"
Meta-objects configuration
The connector uses meta-object entries
to determine which business object to associate with a message.
The type of business object and verb used in processing an event message
is based on the FORMAT field contained in the WebSphere MQ message header.
{MQMD.Format}
You construct a meta-object attribute to store the business object name
and verb to associate with the WebSphere MQ message header FORMAT field text.
url [84]
url [85]
About MAPS, you can find the source files in Java
in the workspace directory of the project.
For example, for the OTA project,
you can find it in the directory
C:\IBM\WebSphereServer\Tools\ies301\Workspace\DECEMBER2007\Maps\Src.
About Business Object,
from the System Mananager you must select
the business object you want to export,
double-click on it to open the Business Object Designer,
then from file menu
you can select 'Save Copy to File'
that you can use to save the business object in single file,
in different format (xsd, xsl, txt..)
or 'Copy All to One File'
to export in only one file
the principal business object with all the related business objects.
Running ICS components as Windows services . How to install and configure WebSphere Business Integration Adapter as Windows service.
Després de escriure al SAP, el ICS escolta per rebre la seva resposta al port definit a RfcProgramId, ("Connector Specific Parameters") que ha de ser únic per a ell.
To start or stop the RFC trace, start System Manager, select specific project under "User Projects" , open Connectors folder and double-click on the specific SAP adapter. "Connection Configuration Express" comes up, and at the "Connector Specific Parameters" tab we can select "RfcTraceOn" as "true". The "*.RFC" files are written the default directory : "\Connectors\SAPnn\"
The MQ Adapter works as follows:
The type of business object and verb used in processing a message
is based on the FORMAT field contained in the WebSphere MQ message header.
The connector uses meta-object entries to determine business object name and verb.
You construct a meta-object
to store the business object name and verb
to associate with the WebSphere MQ message header FORMAT field text.
The actual connector is using a "Data Handler for XML" that has an Attribute "Name Pattern" defined as "HITISoperation::Attrbitute[OperationName].value"
NameHandlerClass = PatternMatchNameHandler
|
|
|
Updated : 8/5/2012.
|
|