ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

Directory Integrator > Previous versions > Version 6.1.1 > Reference Guide > SAP R/3 Component Suite
Directory Integrator, Version 6.1.1

ALE Intermediate Document (IDOC) Connector for SAP R/3 and SAP ERP
This section describes the configuration and operation of the IBM(R) Tivoli(R) Directory Integrator Connector for processing ALE IDOCs sent from an SAP R/3 or ERP system. The chapter contains the following sections: Introduction Configuration Using the SAP ALE IDOC Connector Introduction In an SAP System the Application Link Enabling (ALE) is one of the core integration technologies. It involves the exchange of hierarchical data documents known as Intermediate Documents (IDOCs). There are two scenarios, inbound to SAP, and outbound from SAP. This release of the connector only integrates with IDOCs that are outbound from SAP, and inbound to IBM Tivoli Directory Integrator. This document will use the term inbound with reference to inbound to IBM Tivoli Directory Integrator. The SAP System will always be the IDOC client with IBM Tivoli Directory Integrator acting as the IDOC Server. The IDOC is sent to IBM Tivoli Directory Integrator as an asynchronous event, and when received, IBM Tivoli Directory Integrator pushes the IDOC data onto an AssemblyLine for processing as desired. As it is asynchronous communication, IBM Tivoli Directory Integrator will not provide a response to the client SAP system. SAP TID management is used to ensure data consistency between the SAP system client and IBM Tivoli Directory Integrator. Due to the asynchronous communication the Connector supports only Iterator mode. When configuring ALE in an SAP System, the core task is to create what is called a distribution model. There are many pre-defined distribution models available as standard in an SAP system, but there is also the ability to create a customizable distribution model of your own. The core use of this connector is as an external application that acts as a logical system within the chosen SAP distribution model. The examples provided in this chapter will define integration into a custom SAP HR distribution model, and the pre-defined SAP Central User Management (CUA) distribution model. Of course the connector could be used for integration into any of the other SAP distribution models to access the master data for other SAP modules such as SAP FI/CO or SAP PP. For detailed information on SAP modules visit the SAP help site at http://help.sap.com. Almost any SAP master data business object with an IDOC interface can be exchanged this way. Central to creating or configuring an SPA distribution model are the IDOC message types you want to support. What the connector provides is an XML version of the IDOC, which must be parsed accordingly. To facilitate parsing of the IDOC XML data the connector has been enabled to make use of the IBM Tivoli Directory Integrator XML parsers. You have the choice of the DOM Parser, the SAX Parser or the XSLT Parser. Using these will enable you to extract the required data from the IDOC for you business purpose. For example you may wish to extract particular infotypes from the SAP HR IDOC message type HRMD_A to forward on to IBM Tivoli Identity Manager for automated provisioning purposes. The figure below illustrates the interaction with the SAP System IDOC client and the IBM Tivoli Directory Integrator IDOC server. Figure 4. Interaction with the SAP System IDOC client and the IBM Tivoli Directory Integrator IDOC server

1 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

Configuration The SAP ALE IDOC Connector for SAP R/3 may be added directly into an assembly line. The following section lists the configuration parameters the connector.
IDOC Server Parameters

IDOC Server SAP Gateway Host A mandatory RFC Server Connection attribute that defines the host system that is the SAP Gateway. IDOC Server SAP Gateway Service A mandatory RFC Server Connection attribute that defines the SAP Gateway Service. IDOC Server Program ID A mandatory RFC Server Connection attribute that Defines the Server Program ID that is used in the configuration of the required TCP/IP RFC Destination to register the Server with the SAP Gateway. IDOC Server Unicode Connection? An optional RFC Server Connection attribute that defines the host system that is the SAP Gateway. IDOC Server Optional Connection Parameters An optional RFC Server Connection attribute used to define a list of other optional RFC connection parameters. The value for this configuration list is a key=value list where each connection parameter is separated by the space character. For example the following string value would set the SAP System number to "00" and enable the RFC trace mechanism:
"jco.server.trace=1 jco.server.sysnr=00"
IDOC Client Configuration Parameters

IDOC Client Number A mandatory RFC Client Connection attribute that defines the SAP Systems client. Consists of a 3 digit string value such as "000" or "100" defining the logon client. IDOC Client User A mandatory RFC Client Connection attribute that defines the SAP User Account logon id. Typically this would be a SAP User Account type of Communication or CPIC, although the Dialogue type can be used IDOC Client Password A mandatory RFC Client Connection attribute that defines the SAP User Account password. IDOC Client Lang A mandatory RFC Client Connection attribute that defines the logon language. IDOC Client Hostname A mandatory RFC Client Connection attribute that defines the hostname for the target SAP System. IDOC Client System Number A mandatory RFC Client Connection attribute that defines the system identifier (SID) for the target SAP System. IDOC Client SAP Gateway Service An optional RFC Client Connection attribute that defines the SAP Gateway Service. In most cases this will have the same value as the IDOC Server SAP Gateway Service. IDOC Client SAP Gateway Host An optional RFC Client Connection attribute that defines the SAP Gateway hostname. IDOC Client Max Connections A mandatory RFC Client Connection attribute that defines the maximum number of RFC connections supported by the internal connection pool. IDOC Client Optional Connection Parameters An optional RFC Client Connection attribute used to define a list of other optional RFC connection parameters. The value for this configuration list is a key=value list where each connection parameter is separated by the space character. For example the following string value would turn on the RFC trace mechanism and enable the use of the SAP GUI if it was installed on the same host as IBM Tivoli Directory Integrator.

2 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

"jco.client.trace=1 jco.client.use_sapgui=1"

The following is a list of optional SAP Java Connector parameters that are accessible. Alias user name [jco.client.alias_user] SAP message server [jco.client.mshost] RFC trace [jco.client.trace] Initial codepage in SAP notation [jco.client.codepage] Secure network connection (SNC) mode, 0 (off) or 1 (on) [jco.client.snc_mode] SNC partner, e.g. p:CN=R3, O=XYZ-INC, C=EN [jco.client.snc_partnername] SNC level of security, 1 to 9 [jco.client.snc_qop] SNC name. Overrides default SNC partner [jco.client.snc_myname] Path to library, which provides SNC service [jco.client.snc_lib] SAP R/3 name [jco.client.r3name] Group of SAP application servers [jco.client.group] Program ID of external server program [jco.client.tpname] Host of external server program [jco.client.tphost] Type of remote host 2 = R/2, 3 = R/3, E = External [jco.client.type] Enable ABAP debugging 0 or 1 [jco.client.abap_debug] Use remote SAP graphical user interface (0/1/2) [jco.client.use_sapgui] Get/Don't get a SSO ticket after logon (1 or 0) [jco.client.getsso2] Use the specified SAP Cookie Version 2 as logon ticket [jco.client.mysapsso2] Use the specified X509 certificate as logon ticket [jco.client.x509cert] Enable/Disable logon check at open time, 1 (enable) or 0 (disable) [jco.client.lcheck] String defined for SAPLOGON on 32-bit Windows [jco.client.saplogon_id] Data for external authentication (PAS) [jco.client.extiddata] Type of external authentication (PAS) [jco.client.extidtype] Idle timeout (in seconds) for the connection after which it will be closed by R/3. Only positive Enable (1) or Disable (0) dsr support [jco.client.dsr]
General Configuration Parameters

IDOC As XML Only? A general attribute that defines if only the XML valued attribute for the IDOC is required. If set to "No", the IDOC control data will be set as independent attributes within the resulting Entry for each IDOC. If set to "Yes", only one attribute (idoc.xml) is created for the IDOC which contains the IDOC content as an XML valued string. Process SAP RFM Requests? A general attribute that defines if the Connector will also process remote function module (RFM) calls made on it. If set to "Yes" all RFM calls will be added to an Entry which contain one attribute (rfm.xml) which is the content of the RFM as an XML valued string. If set to "No" then RFM requests on the IDOC Server will be ignored. Note: The processing performed for RFM calls is merely to provide the RFM as an XML valued attribute. The IDOC Server does not currently attempt to populate the export and table arguments of the RFM call. If required this can be provided under an enhancement of the Connector. To do this contact IBM Support. Only RFM calls that form part of an ALE distribution models internal process should be considered. Parse IDOC or RFM XML? A general attribute that defines if parsing is to be attempted on the XML valued attributes idoc.xml and rfm.xml. You must have one of the available IBM Tivoli Directory Integrator parsers configured to interact with the Connector in your AssemblyLine configuration. Enable JCo Middleware Trace Logging? A general attribute that defines if the available JCo trace logs are to be enabled and included in the AssemblyLine logging and tracing. JCo Middleware Trace Level A general attribute that defines the JCo middleware trace level. JCo Middleware Trace File Path A general attribute that defines the directory where the JCo middleware trace file will be created. Also used to store RFM requests as a file with XML content. Using the SAP ALE IDOC Connector This section describes details on using the Connector in the supported Iterator mode. Also described is the

3 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

IBM Tivoli Directory Integrator schema supported by the Connector.

IBM Tivoli Directory Integrator schema

The schema for the Connector is centred on providing an AssemblyLine with Entries, where each represents and individual IDOC. An IDOC itself contains 3 sections of data. These are Control Data, Segment Data, and Status Data. The simplest and most effective way of representing this data in IBM Tivoli Directory Integrator is an XML format, which can be easily dissected for the required data. As the control data is readily accessible, and can provide useful standalone information, this data is also available as individual attributes. The configuration parameter "IDOC As XML Only?" is used to enable or disable the production of the control data as stand alone attributes. As the Connector is also able to accept Remote Function Module requests, there is a requirement to represent the data in one or more attributes. Currently the content of an RFM will be available as a single XML valued attribute. The configuration parameter "Process SAP RFM Requests?" is used to enable or disable the production of the RFM XML valued attribute. The table below defines the schema available to this Connector. Table 46. SAP ALE IDOC Connector Schema
Attribute Name idoc.tid idoc.xml idoc.segments.xml idoc.ctrl.ArchiveKey idoc.ctrl.Client idoc.ctrl.CreationDate idoc.ctrl.CreationTime idoc.ctrl.Direction idoc.ctrl.EDIMessage idoc.ctrl.EDIMessageGroup idoc.ctrl.EDIMessageType idoc.ctrl.EDIStandardFlag idoc.ctrl.EDIStandardVersion idoc.ctrl.EDITransmissionFile idoc.ctrl.ExpressFlag idoc.ctrl.IDocCompoundType idoc.ctrl.IDocNumber idoc.ctrl.IDocSAPRelease idoc.ctrl.IDocType idoc.ctrl.IDocTypeExtension Attribute Description Input schema attribute whose value is the associated TID value provided by the SAP System Client. Input schema attribute whose value is the complete IDOC in XML format. Input schema attribute whose value is the complete Segment hierarchy in XML format. No control attribute values are contained in this XML. Input schema attribute whose value represents the IDOC control data archive key (the value of the field "ARCKEY"). Input schema attribute whose value represents the IDOC control data client (the value of the field "MANDT"). Input schema attribute whose value represents the IDOC control data creation date (the value of the field "CREDAT"). Input schema attribute whose value represents the IDOC control data creation time (the value of the field "CRETIM"). Input schema attribute whose value represents the IDOC control data direction (the value of the field "DIRECT"). Input schema attribute whose value represents the IDOC control data EDI message (the value of the field "REFMES"). Input schema attribute whose value represents the IDOC control data EDI message group (the value of the field "REFGRP"). Input schema attribute whose value represents the IDOC control data EDI message type (the value of the field "STDMES"). Input schema attribute whose value represents the IDOC control data EDI standard flag (the value of the field "STD"). Input schema attribute whose value represents the IDOC control data EDI standard version (the value of the field "STDVRS"). Input schema attribute whose value represents the IDOC control data EDI transmission file (the value of the field "REFINT"). Input schema attribute whose value represents the IDOC control data express flag (the value of the field "EXPRSS"). Input schema attribute whose value represents the IDOC control data IDOC compound type (the value of the field "DOCTYP"). Input schema attribute whose value represents the IDOC control data IDOC number (the value of the field "DOCNUM"). Input schema attribute whose value represents the IDOC control data IDOC SAP release (the value of the field "DOCREL"). Input schema attribute whose value represents the IDOC control data IDOC type (the value of the field "IDOCTYP"). Input schema attribute who's value represents the IDOC control data IDOC type extension that is also known as CIM type or customer extension type (the value of the field "CIMTYP"); Input schema attribute whose value represents the IDOC control data message code (the value of the field "MESCOD"). Input schema attribute whose value represents the IDOC control data message function (the value of the field "MESFCT"). Input schema attribute whose value represents the IDOC control data message type (the value of the field "MESTYP"). Input schema attribute whose value represents the IDOC control data output mode (the value of the field "OUTMOD"). Input schema attribute whose value represents the IDOC control data recipient address (the value of the field "RCVSAD"). Input schema attribute whose value represents the IDOC control data logical recipient address (the value of the field "RCVLAD"). Input schema attribute whose value represents the IDOC control data recipient partner function (the value of the field "RCVPFC"). Attribute Syntax java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string

idoc.ctrl.MessageCode idoc.ctrl.MessageFunction idoc.ctrl.MessageType idoc.ctrl.OutputMode idoc.ctrl.RecipientAddress idoc.ctrl.RecipientLogicalAddress idoc.ctrl.RecipientPartnerFunction

java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string

4 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

Attribute Name idoc.ctrl.RecipientPartnerNumber idoc.ctrl.RecipientPartnerType idoc.ctrl.RecipientPort idoc.ctrl.SenderAddress idoc.ctrl.SenderLogicalAddress idoc.ctrl.SenderPartnerFunction idoc.ctrl.SenderPartnerNumber idoc.ctrl.SenderPartnerType idoc.ctrl.SenderPort idoc.ctrl.Serialization idoc.ctrl.Status idoc.ctrl.TableStructureName idoc.ctrl.TestFlag rfm.xml

Attribute Description Input schema attribute whose value represents the IDOC control data recipient partner number (the value of the field "RCVPRN"). Input schema attribute whose value represents the IDOC control data recipient partner type (the value of the field "RCVPRT"). Input schema attribute whose value represents the IDOC control data recipient port (the value of the field "RCVPOR"). Input schema attribute whose value represents the IDOC control data sender address (the value of the field "SNDSAD"). Input schema attribute whose value represents the IDOC control data logical sender address (the value of the field "SNDLAD"). Input schema attribute whose value represents the IDOC control data sender partner function (the value of the field "SNDPFC"). Input schema attribute whose value represents the IDOC control data sender partner number (the value of the field "SNDPRN"). Input schema attribute whose value represents the IDOC control data sender partner type (the value of the field "SNDPRT"). Input schema attribute whose value represents the IDOC control data Returns the sender port (the value of the field "SNDPOR"). Input schema attribute whose value represents the IDOC control data serialization (the value of the field "SERIAL"). Input schema attribute whose value represents the IDOC control data status (the value of the field "STATUS"). Output schema attribute whose value represents the IDOC control data table structure name (the value of the field "TABNAM"). Input schema attribute whose value represents the IDOC control data test flag (the value of the field "TEST"). Input schema attribute whose value represents the complete content of an RMF request in XML format.

Attribute Syntax java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string java.lang.string

Attributes of type java.lang.String can be of arbitrary length.

XML Attribute Parsing

The main mode of operation for the connector is the production of the XML valued attributes that represent the complete content of an IDOC, or RFM. As a result the best way to handle this data is with one of the available IBM Tivoli Directory Integrator XML Parsers attached to the Connector. Due to the nested nature of the resulting XML, the DOM parser is not recommended, but still can be used. The recommended parsers are the SAX Parser or the XSLT Parser depending on the type of SAP ALE distribution model the Connector is to integrate with. If the Connector has to handle multiple IDOC message types, or is configured to process RFM requests, then the SAX Parser is recommended. This is because you will have different XML schemas for the different IDOC message types, and the RFM XML. The SAX Parser is the only IBM Tivoli Directory Integrator parser that can handle XML values with different XML schemas. You do this by not configuring the SAX Parser to have a specific value for it's "Group" configuration parameter. This has the effect of not having to define a particular root element. If you are certain that the Connector will process only one type of IDOC, then you can use the XSLT Parser, which allows for a more complete Connector Entry to Work Entry attribute mapping. For example if the Connector was configured to be the recipient of SAP HR Master Data, then you would only ever expect to see IDOCs of the message type HRMD_A. At the time this connector was developed the latest version of this message type was HRMD_A06. You could then use and XSL like the following to parse the IDOCs contents for the required data.
<XSL:stylesheet xmlns:XSL="http://www.w3.org/1999/XSL/Transform" version="1.0"> <XSL:output method="XML" indent="yes" /> <XSL:template match="HRMD_A06"> <DocRoot> <Entry> <XSL:apply-templates select="./IDOC"/> </Entry> </DocRoot> </XSL:template> <XSL:template match="IDOC"> <XSL:apply-templates select="./EDI_DC40"/> <XSL:apply-templates select="./E1PLOGI"/> </XSL:template> <XSL:template match="EDI_DC40"> <Attribute name="IDOC_CTRL_DOCNUM"> <XSL:for-each select="DOCNUM"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each>

5 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

</Attribute> <Attribute name="IDOC_CTRL_MANDT"> <XSL:for-each select="MANDT"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="IDOC_CTRL_DOCREL"> <XSL:for-each select="DOCREL"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="IDOC_CTRL_IDOCTYP"> <XSL:for-each select="IDOCTYP"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="IDOC_CTRL_SNDPOR"> <XSL:for-each select="SNDPOR"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="IDOC_CTRL_RCVPOR"> <XSL:for-each select="RCVPOR"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:template> <XSL:template match="E1PLOGI"> <XSL:apply-templates select="./E1PITYP"/> </XSL:template> <XSL:template match="E1PITYP"> <XSL:apply-templates select="./E1P0002"/> <XSL:for-each select="E1P0105"> <Attribute name="PR_COMM_SUBTY"> <XSL:for-each select="SUBTY"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="PR_COMM_USRID"> <XSL:for-each select="USRID"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="PR_COMM_USRID_LONG"> <XSL:for-each select="USRID_LONG"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:for-each> </XSL:template> <XSL:template match="E1P0002"> <Attribute name="PR_PERNR"> <XSL:for-each select="PERNR"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each>

6 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

</Attribute> <Attribute name="PR_LASTNAME"> <XSL:for-each select="NACHN"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="PR_FIRSTNAME"> <XSL:for-each select="VORNA"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="PR_BIRTHDATE"> <XSL:for-each select="GBDAT"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:template> </XSL:stylesheet>

If the IDOC message type was always going to be the USERCLONE message type, then you could use XSL like the following to get the required attribute mappings.
<XSL:stylesheet xmlns:XSL="http://www.w3.org/1999/XSL/Transform" version="1.0"> <XSL:output method="XML" indent="yes" /> <XSL:template match="USERCLONE05"> <DocRoot> <Entry> <XSL:apply-templates select="./IDOC"/> </Entry> </DocRoot> </XSL:template> <XSL:template match="IDOC"> <XSL:apply-templates select="./EDI_DC40"/> <XSL:apply-templates select="./E1BPBNAME"/> <XSL:apply-templates select="./E1BPLOGOND"/> <XSL:apply-templates select="./E1BPADDR3"/> <XSL:apply-templates select="./E1BPLOGOND"/> <XSL:apply-templates select="./E1BPUSCOMP"/> </XSL:template> <XSL:template match="EDI_DC40"> <Attribute name="TDI_DOCNUM"> <XSL:for-each select="DOCNUM"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_MANDT"> <XSL:for-each select="MANDT"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_DOCREL"> <XSL:for-each select="DOCREL"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_IDOCTYP"> <XSL:for-each select="IDOCTYP"> <Value> <XSL:value-of select="." />

7 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

</Value> </XSL:for-each> </Attribute> <Attribute name="TDI_USERCLONE"> <XSL:for-each select="USERCLONE"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_SNDPOR"> <XSL:for-each select="SNDPOR"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_RCVPOR"> <XSL:for-each select="RCVPOR"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:template> <XSL:template match="E1BPBNAME"> <Attribute name="TDI_BAPIBNAME"> <XSL:for-each select="BAPIBNAME"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:template> <XSL:template match="E1BPLOGOND"> <Attribute name="TDI_CLASS"> <XSL:for-each select="CLASS"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_TZONE"> <XSL:for-each select="TZONE"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:template> <XSL:template match="E1BPADDR3"> <Attribute name="TDI_FIRSTNAME"> <XSL:for-each select="FIRSTNAME"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <Attribute name="TDI_LASTNAME"> <XSL:for-each select="LASTNAME"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> <XSL:apply-templates select="./E1BPADDR1"/> </XSL:template> <XSL:template match="E1BPADDR1"> <Attribute name="TDI_E_MAIL"> <XSL:for-each select="E_MAIL"> <Value> <XSL:value-of select="." />

8 of 9

3/5/2012 10:15 AM

ALE Intermediate Document (IDOC) Connector for SAP...

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1...

</Value> </XSL:for-each> </Attribute> </XSL:template> <XSL:template match="E1BPUSCOMP"> <Attribute name="TDI_COMPANY"> <XSL:for-each select="COMPANY"> <Value> <XSL:value-of select="." /> </Value> </XSL:for-each> </Attribute> </XSL:template> </XSL:stylesheet>
Configuration in SAP ALE Distribution Models

To enable the connector to be part of an SAP ALE distribution model the Connector must be setup as a logical system on the SAP system. To do this to actions are required. 1. An RFC Destination of type TCP/IP is created where the Connector is registered as an external program. Take care to make sure that the program name provided in the RFC Destination, is the same value you give to the Connector configuration parameter "IDOC Server Program ID". To test the RFC connection ensure the Connector is running in an IBM Tivoli Directory Integrator AssemblyLine. This AssemblyLine may be bare bones one with only the connector, and possibly a script component to dump the resulting work entry attributes. Create RFC Destinations using SAP GUI transaction SM59. 2. A logical System is created that has the same name as the RFC Destination created in step 1. This is done using SAP GUI transaction SALE. You don't need to assign a client to the logical system like you do for other SAP logical systems that actually represent a real SAP System client. Once the logical system is in place you can pretty much use it as you would any other logical system in an SAP ALE distribution model. The Connector has been tested as part of a SAP HR Master Data distribution model, and as part of the pre-defined SAP CUA distribution model. If you run into other issues using other SAP ALE distribution models please contact IBM Support. This is a new Connector for IBM Tivoli Directory Integrator and will no doubt have some teething issues.
[ Top of Page | Previous Page | Next Page | Contents | Terms of use | Feedback ] (C) Copyright IBM Corporation, 2003, 2007. All Rights Reserved. IBM Tivoli Direc tory Integrator 6.1.1

9 of 9

3/5/2012 10:15 AM