SAP NetWeaver 7.31 SAP NetWeaver Process Integration Simple Use Cases for B2B OFTP Configuration 1
TABLE OF CONTENTS 1 PREFACE... 3 2 INTRODUCTION AND PREREQUISITES... 3 2.1 Introduction... 3 2.1.1 OFTP Adapter... 4 2.2 Prerequisites... 5 2.2.1 General Prerequisites... 5 2.2.2 Prerequisites for Generation of OFTP Test Keys with Extended Key... 6 2.2.3 Prerequisites for Import of SSL/CMS Certificates... 7 2.2.4 Prerequisites for Import of B2B Seed file for VDA tables... 7 2.2.5 Providing the necessary User and Authorizations... 7 2.2.6 Setting Up the File Directories... 7 2.2.7 Adding Software Components to PI B2B ADDON product... 8 3 VARIANT 1: PARTNER 1 & PARTNER 2 VIA TCP/IC TRANSPORT WITH VDA CONVERTER MODULE USING VDA FORMAT FILE... 8 3.1 Design Object Used... 9 3.2 Configuring the Process Integration Scenario... 9 3.2.1 Calling the Process Integration Designer... 9 3.2.2 Creating the Business Components... 9 3.2.3 Creating the Integration Flow for Partner 1... 9 3.2.4 Creating Channels for Partner 1 Integration Flow... 10 3.2.5 Creating the Integration Flow for Partner 2... 13 3.2.6 Creating Channels for Partner 2 Integration Flow... 13 3.2.7 Activating the Configuration Objects... 16 4 VARIANT 2: PARTNER 1 & PARTNER 2 VIA TCP/IP TRANSPORT WITH ODETTE CONVERTER MODULE USING ODETTE FORMAT FILE... 17 4.1 Design Objects Used... 17 4.2 Configuring the Process Integration Scenario... 17 4.2.1 Calling the Process Integration Designer... 17 4.2.2 Creating the Business Components... 17 4.2.3 Creating the Integration Flow for Partner 1... 17 4.2.4 Creating Channels for Partner 1 Integration Flow... 18 4.2.5 Creating the Integration Flow for Partner 2... 21 4.2.6 Creating Channels for Partner 2 Integration Flow... 21 4.2.7 Activating the Configuration Objects... 24 4.3 Executing the Use Case... 25 4.3.1 Channel Monitoring... 25 4.3.2 Message Monitoring... 25 5 VARIANT 3: PARTNER 1 & PARTNER 2 VIA ISDN TRANSPORT PROTOCOL... 26 5.1 ISDN Connectivity... 26 5.2 Configuring the Process Integration Scenario... 27 5.2.1 Calling the Process Integration Designer... 27 5.2.2 Creating the Business Components... 27 5.2.3 Creating the Integration Flow for Partner 1... 27 5.2.4 Creating Channels for Partner 1 Integration Flow... 28 5.2.5 Creating the Integration Flow for Partner 2... 30 5.2.6 Creating Channels for Partner 2 Integration Flow... 31 5.2.7 Activating the Configuration Objects... 33 5.3 Executing the Use Case... 33 5.3.1 Channel Monitoring... 34 5.3.2 Message Monitoring... 34 2
1 Preface Constraints The texts, references, and graphics contained in this manual have been compiled with utmost care; nevertheless, it is impossible to guarantee that they are fully without error. SAP cannot assume any responsibility for the correctness or completeness of the following documentation; the user alone is responsible for verifying the information contained therein. SAP will only assume liability for damage arising from the use of this documentation irrespective of the pertinent legal basis in the case of intentional or active negligence; under no other circumstances will a warranty be made. Definition This manual describes simple application cases for OFTP (Odette File Transfer Protocol) adapter with VDA converter Module. The scenario is configured using Integration Flow for process integration and all the configuration steps that are necessary to execute the application cases on the basis of SAP NetWeaver 7.31. Intended Audience This manual is intended to be used by both technology and application consultants. Structure The structure of this document follows the sequence of steps required to configure and run the use cases. Additional Documentation List of related documentation Documentation SAP NetWeaver Documentation Simple Use Cases Purpose Introduction to Simple Use Cases and description of the simple use case scenarios for Process Integration 2 Introduction and Prerequisites 2.1 Introduction Use cases are based on simple examples that enable you to learn the main features of PI B2B using iflow Configuration for the Advanced Adapter Engine Extended. These instructions will enable you to understand, configure, and execute simple scenarios (that are based on fundamental communication patterns), as well as check that the scenarios are executed correctly. The prerequisite for this document is that you have a general understanding of SAP NetWeaver Process Integration along with new B2B adapter and B2B modules. The following use case variants for the Advanced Adapter Engine Extended are available at present: Variants Variants 1: Partner 1 & Partner 2 via TCP/IC transport with VDA Converter Module using VDA format file Variant 2: Partner 1 & Partner 2 via TCP/IC transport with Odette Converter Module using Odette format file Description OFTP sender and receiver using TCP/IP transport and VDA Converter module to transfer VDA format file. OFTP sender and receiver using TCP/IP transport and Odette Converter module to transfer Odette format file 3
Variant 3: Partner 1 & Partner 2 via ISDN transport for SAP PI system in DMZ Environment OFTP sender and receiver using ISDN transport You can aim to learn about the following with the use cases: Working with OFTP adapter with the Process Integration Designer in NWDS: Configuring simple scenarios and understanding created configuration objects Working with B2B converter module VDA Converter Module within B2B adapters Working with the runtime: Executing the use cases and checking the results by using the monitoring tools 2.1.1 OFTP Adapter OFPT adapter has been designed as an integrated SAP NW PI adapter and developed for direct integration in the SAP Adapter Framework. Using OFTP adapter, it will be possible for all incoming and outgoing OFTP messages to make optimal use of the extensive monitoring and alerting functionalities of the central process integration platform. OFTP2 adapter is downwardly compatible, and thus supports all protocol versions of the 1.X series (RFC 2204, RFC 5024) in addition to OFTP 2.0. Certification by Odette Ltd. International guarantees complete compatibility with OFTP software from other manufacturers. Particularly in the field of data security, the OFTP2 protocol the successor of OFTP offers many advantages: modern mechanisms such as encryption of the transport layer by means of TLS as well as encryption, signature and compression at message level via CMS ensure the confidentiality and authenticity of your data, even via high-speed and cost-effective Internet connections via TCP/IP. In addition, OFTP2 s dedicated end-to-end responses guarantee confirmed data receipt. The opportunity to use different certificates for the security mechanisms ensures a very high degree of security, even in complex infrastructures similar to any other standard module that can be used in the channel configuration. It also has possibility to archive the payload of the message with the name and location configured in the module parameters. Unlike other certificate-based cryptographic protocols, OFTP2 also implements automatic certificate exchange: once a connection has been created, your partners certificates are automatically filled away in the secure keystore and can be used without any production downtime. This means that certificates do not have to be exchanged manually. Authentication of the partners against the trusted services list administered by Odette Ltd. Reduces the user s own workload while maintaining the highest possible security. OFTP2 standalone gateway 4
In addition to the certified OFTP2 adapter, OFTP2 standalone gateway is also offered. The gateway can be used for OFTP2 communication in the DMZ if there is to be no direct connection between SAP NW PI and external partners. Compared with a Decentral adapter engine, it offers lower hardware requirements, and a single gateway can be used to connect several PI systems. Both products are optimally matched to each other, and implement their OFTP2 communication easily and efficiently. Briefly OFTP2 Adapter supports the following features -> OFTP Version 1.4 and 2.0 Support TCP/IP and ISDN (including X.25) PI Archiving on both the directions File Formats (Unstructured, Fixed Length, Variable & Text) Encoding (EBCDIC & ISO-8859-1) Buffer Compression Versions can be negotiated between trading partners Force Incoming End Response (EERP/NERP) Suppress End Response (EERP/NERP) Signed End Response (EERP/NERP) CMS (Cryptographic Message Syntax) Encryption (Symmetric & Asymmetric) Signing Secure Authentication Message Compression OFTP Log Viewer Overview of OFTP2 Communication -> Start Session o Start File Data Transfer o End File End Session 2.2 Prerequisites 2.2.1 General Prerequisites To configure and execute the use cases, SAP Net Weaver with usage type Advanced Adapter Engine Extended must be correctly installed and configured. The following table lists the prerequisites and the relevant guides: List of required steps Step 1. You have installed the Advanced Adapter Engine Extended. Documentation You can find the corresponding guides on SAP Service Marketplace in the Implementation Documentation Center for SAP NetWeaver 7.3 and SAP NetWeaver 7.3 including Enhancement Package 1 5
2. You have installed the B2B Add-on. You can download the B2B add-on from the following location: http://service.sap.com/swdc -> Installation and Upgrades -> Browse our Download Catalog - > SAP NetWeaver and complementary products -> PI B2B ADDON and PI SFTP PGP ADDON. For downloading latest Support package and patches, please refer to the following location -> http://service.sap.com/swdc -> Support Packages and Patches -> Browse our Download Catalog -> SAP NetWeaver and complementary products -> PI B2B ADDON and PI SFTP PGP ADDON 3. You have imported the content for the Enterprise Services Repository corresponding to the latest support package/patch into the Advanced Adapter Engine Extended System. 4. You have configured the System Landscape Directory (SLD) for the Advanced Adapter Engine Extended System. 5. You have installed the NetWeaver Developer Studio. 6. The JVM should be installed with unlimited JCE policy. SAP Note 836200 The simple use cases are located in the Enterprise Services Repository in below software components SAP BASIS, software component version SAP BASIS 7.31, namespaces http://sap.com/xi/xi/system/patterns SFTP ADAPTER, software component version SFTP ADAPTER 1.0, namespaces http://sap.com/xi/xi/sftp B2B MAPPING KIT, software component version B2B MAPPING KIT 1.0, namespaces http://sap.com/xi/b2b/mappingfunctions Configuring, Working with and Administering System Landscape Directory You can find the corresponding guides on SAP Service Marketplace at https://service.sap.com/installnw73 Under Installation - Standalone Engines and Clients Installation Clients Inst. and Update - SAP NetWeaver Developer Studio 7.3 EHP1. Refer SAP Note 1240081 - Java Cryptography Extension (JCE) Jurisdiction Policy. Note that you set up the use cases in your development or test system, but not in your productive system. 2.2.2 Prerequisites for Generation of OFTP Test Keys with Extended Key OFTP keys pair s needs to be created with extended key usage type for this use case. Refer the following link to create a test keys pair with an unsupported 3 rd party tool. http://wiki.sdn.sap.com/wiki/display/xi/generating+oftp+test+keys+with+extended+key+usage These keys should be used for testing purpose only. For production use, keys should be obtained from Odette representing individual trading partners. 6
2.2.3 Prerequisites for Import of SSL/CMS Certificates After creation of test keys pair for OFTP, they have to be imported into NWA Key Storage of the PI system. This has to be done for both SAP PI System (Normal and in DMZ environment). Refer following link for step by step procedure. http://wiki.sdn.sap.com/wiki/display/xi/importing+oftp+test+keys+into+nwa+key+storage In this use case, we are using same system as two different trading partners. Hence NWA Key Storage View for both Partner1 and Partner2 has to be created using the same Private and Public Key Certificates. 2.2.4 Prerequisites for Import of B2B Seed file for VDA tables Data within VDA tables has to be generated for usage of VDA converter module within PI server. Hence B2B seed file will be used in this use case to generate entries within VDA tables. Follow the below URL. http(s)://<host>:<port>/webdynpro/resources/sap.com/converter~maintain~maintenanceapp/maintenance Click on VDA -> Tables -> Import. Browse and select B2B seed file for VDA. Select checkbox Overwrite duplicate Keys and click on Import. Message for successful import will be displayed. 2.2.5 Providing the necessary User and Authorizations To log on to the AEX system to configure the simple use cases, you have to create a user XIDEMO with the following roles in the Advanced Adapter Engine Extended: SAP_XI_CONFIGURATOR_J2EE SAP_XI_MONITOR_J2EE 2.2.6 Setting Up the File Directories The variants are based on a very simple system landscape that comprises various different file systems (on the host of the SAP system on which the Advanced Adapter Engine Extended is installed) for both Sender and Receiver File Adapter. When the use cases are executed, files are moved between file directories. Therefore, to be able to configure the use cases, the file directories must have been created and described in the System Landscape Directory. Only then can you access the directories during configuration in the Process Integration Designer. Perform the steps below to create the required directories on the host of the SAP system on which the Advanced Adapter Engine Extended is installed. 1. Open the file directory of the SAP system, on which the Advanced Adapter Engine Extended is installed. e.g. using Windows Explorer on Windows Systems. 2. Create a directory in which you can save files temporarily and create sub directories B2B in it. Create another subdirectory in B2B as OFTP. A work directory already exists on many computers that can be used for this purpose and under which you can create the required directories. 3. Create three further sub directories in the sub directory OFTP. Suggested names: Sender, Receiver and Archive. You must have authorization to access this directory to be able to test the process integration scenario. Bear this in mind when you define the directory, and, if applicable, contact your system administrator. 4. Copy the following files to directory Sender ZB2B_VDA.txt ZB2B_Odette.txt 7
5. Create three further sub directories in the sub directory Archive. Suggested names: Send, Receive and Error. 6. Create directories as per step 1, 2 &3 on DMZ located SAP PI Advanced Adapter Engine Extended system. In case you do not have access to the file directory of SAP PI system located in DMZ location, ask your administrator. 7. Copy the following files to directory Sender ZXiPatternSenderFile1.xml ZXiPatternSenderFile2.xml ZXiPatternSenderFile3.xml These files are provided by SAP in a ZIP file. The ZIP file for 7.31 containing also the EOIO test files is available in SAP Developer Network (SDN) and can be found using the direct link EHP 1 for SAP NetWeaver Process Integration 7.3 Test Files for Simple Use Cases. 2.2.7 Adding Software Components to PI B2B ADDON product Perform the following steps in the System Landscape Directory (SLD) for the Advanced Adapter Engine Extended: 1. To call the System Landscape Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aex-host>:<aex- Port>/dir. 2. Start the SLD. To do so, on the Advanced Adapter Engine Extended start page, choose System Landscape Directory. 3. Log on using your user you created. 4. On the initial screen of the SLD, choose Products. 5. Filter for PI B2B ADDON product and check for B2B MAPPING KIT 1.0 software component version is available in Software Components tab. If not proceed with below associations steps. 6. Return back to initial screen of SLD by clicking on link to Home. 7. On the initial screen of the SLD, choose CIM Instances. 8. Filter for B2B MAPPING KIT 1.0 for class Software Component Version. 9. Click on New Association. 10. Filter for *B2B* with Association Type Software Features Software Component and Associated Class as Product Instance. 11. Select PI B2B ADDON 1.0: JAVA COMPONENTS and click on Associate. A message for successful association is displayed. 12. Now software component version B2B MAPPING KIT 1.0 will be available in list of Software Components for PI B2B ADDON product. 13. Return back to initial screen of SLD by clicking on link to Home. 3 Variant 1: Partner 1 & Partner 2 via TCP/IC transport with VDA Converter Module using VDA format file This variant enables you to configure and execute message exchange between two Integration Flows acting as two different partners using OFTP adapter via TCP/IP protocol. In Partner1 Integration Flow, File Adapter picks a VDA format file and converts in xml using VDA Converter module within PI Advanced Adapter Engine Extended. On receiver side, OFTP adapter transfer the file to OFTP sender of Partner2 Integration Flow using OFTP protocol which enables secure authentication via Odette ID (SSID), SFID and an additional sender and receiver password 8
authentication. At last file receiver converts the file back to VDA format and copies to the relevant directory. 3.1 Design Object Used 3.2 Configuring the Process Integration Scenario In configuration, you use the design objects in the process integration scenario for the actual system landscape. You have already described the system landscape in the SLD. The communication components defined in this section will enable you to address them as senders/receivers of messages from the in the Process Integration Designer. You perform the following configuration steps in the SAP Process Integration Designer for the Advanced Adapter Engine Extended. 3.2.1 Calling the Process Integration Designer First, open the SAP NetWeaver Developer Studio. Set the connection data for accessing the Integration Directory under the menu Process Integration Change Preferences. The connection details to the Advanced Adapter Engine Extended System have to be maintained using URL or AEX-Host and AEX-Port. To call the SAP Process Integration Designer follow the menu path Window Open Perspective Other SAP Process Integration Designer. Logon to the AEX system using the Menu Process Integration Connect providing your user credentials. appear. Under PI Tools configuration select Tool-Specific. Under Update Local Cache Status click the button Update to Refresh the SLD cache. Click on OK button to close the window. On the Right bottom corner of NWDS the label Updating cache will appear & it will show the status progress. When the cache update finished continue with the next steps. 3.2.2 Creating the Business Components Perform the following steps to create the Business Component: 1. To create the Business Components, select Systems. Right click and select New Business Components options from the context menu. A Pop-up titled Create Business Components will appear. 2. Enter the name of Business Component as <SID>_iFlow_FileSystem_OFTP_Partner1. <SID> is the system ID of the Advanced Adapter Engine Extended System. 3. Click Finish. Business Component details will be open. 4. Within Sender Interface frame, click on Add. Select XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 5. Now click on Add button within receiver interface frame. Select XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31 6. Click on Save button to submit changes to the above created Business Component. 7. Following the above procedure, create three more business components <SID>_iFlow_FileSystem_OFTP_Partner2 <SID>_iFlow_FileSystem_OFTP_Partner5 <SID>_iFlow_FileSystem_OFTP_Partner6 8. Add the service interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31 as Sender and Receiver Interface to the above created Business Components. 3.2.3 Creating the Integration Flow for Partner 1 Perform the following steps to create a Partner 1 integration flow. 1. In the Process Integration Designer choose New Integration Flow ( ). 9
2. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name or the Integration Flow as B2B_OFTPScenario1_Partner1. 3. Choose Next. 2. As Sender Business System select the Business System <SID>_iFlow_FileSystem_OFTP_Partner1 you created using the Browse button. 3. As Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 4. In Tab Receiver Systems select the Business Component <SID>_iFlow_FileSystem_OFTP_Partner1 using the input help for the Receiver Name. 5. As Receiver Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 6. Choose Finish. The integration Flow will be displayed in a graphical overview. 3.2.4 Creating Channels for Partner 1 Integration Flow You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. 1. In the graphical editor, click on channel for the sender component. The Details tab for the channel will open. 2. As Channel Name set FileSender. 3. As Adapter Type select File SAP BASIS 7.31. 4. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see Error! Reference source not found.). In the case of the sender communication channel, enter the whole path for the file directory Sender. Example: C:/<selected path>/b2b/oftp/sender 5. As File Name set VDA.txt. 7. Click on Module tab of the channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/vdaconvertermodule Local Enterprise Bean Vda2xml Use the Move Up button to move module for VDA Converter as first Module. 6. Following the same procedure (see step 1-2), create the communication channel OFTPReceiver of Adapter type OFTP B2B TOOLKIT 1.0 for the receiver Component <SID>_iFlow_FileSystem_OFTP_Partner1. 7. Select TCP/IP as transport protocol and Message Protocol as OFTP 2.0. 8. Click on Adapter Specific tab and enter the following details on subtab General TCP/IP Settings -> Partner host Partners host where OFTP Client should connect TCP/IP Settings -> Port Allowed ports are values in [0;65535]. The default ports are 3305 for plain and 6619 for SSL secured OFTP 10
Checkbox -> Specify Local Host Selected (option through which the outbound communication can happen) Checkbox -> Use SSL Selected (Determines whether the connection should be encrypted using SSL or not) View Containing Trusted Certificates Key store view which contains the trusted certificates (OdetteCertificateExchangeProvider) Connection Settings > Own Odette ID Own Odette-ID (The Odette ID always starts with the letter O followed by a country-specific ID ( 0013 for Germany), a unique, partner specific part and a part everyone may choose freely e.g. O0013SAPPJ8P1) Connection Settings > Partner Odette ID Partner Odette-ID (e.g. O0013SAPPJ8P2) Connection Settings > File Originator (SFIDORIG) Originator SFID as agreed upon with partner. If it s not configured, the corresponding Odette-ID representing each party will be used as a default. Connection Settings > Final File Destination (SFIDDEST) Destination SFID as agreed upon with partner. Connection Settings > Own Password (Sender) Sender password (agreed upon by bilateral agreement) Connection Settings > Partner Password (Receiver) Receiver password (agreed upon by bilateral agreement) File Settings -> Outgoing Virtual File Dataset Name The dataset name of the virtual file which is about to be transferred (e.g. Outfile) File format The format which the file is encoded (e.g. Unstructured) Encoding The type of the data (or) records present in the file which is about to be transferred No conversion (No Encoding) Description The description of the virtual file being transferred Archiving -> Archive Messages Select Checkbox to archive message 11
Incoming Payload to channel Select checkbox and provide Filename information to get the archived file (Refer Step 2.2.6 -> 5 for directory location) Outgoing Wired Message Select checkbox and provide Filename information (Refer Step 2.2.6 -> 5 for directory location) 9. Go to Technical settings subtab and enter the following below details Checkbox -> Allow Compression (1.X RLE) Selected - The location can handle OFTP data buffer compression (Compression is only used if supported by both locations) Checkbox -> Version Negotiable If no OFTP 2.0 security features are enabled, the version is negotiable with the partner Max Credit Count The number of consecutive Data Exchange Buffers sent by the Speaker before it must wait for a Credit (CDT) command from the Listener (default value - 15) Max Exchange Buffer Size The length, in octets, of the largest Data Exchange Buffer that can be accepted by the location. The length includes the command octet but does not include the Stream Transmission Header. After negotiation, the smallest size will be selected. 10. Go to ERP subtab and leave the entries as per default. 11. Go to CMS subtab and enter the following below details KeyStore containing own certificates and keys NWA Key Storage view which contains own certificates and keys KeyStore containing partner certificates NWA Key Storage view which contains partner certificates Checkbox -> Encrypt files Selected (Using this option all files going to be encrypted before being sent. The encryption algorithm has to be set by bilateral agreement) Encryption Algorithm AES (Advanced Encryption Standard) Checkbox -> Sign files Sign the file with SHA1 (Secure Hash Algorithm 1) 12
Use Secure Handshake Authentication Challenge Indicator Use Compression File Compression indicator Request Signed ERP Request for singed ERP/NERP 12. For more information about configuration of OFTP adapter channel, you can refer the following sdn document - http://scn.sap.com/docs/doc-28945. 13. Click on Module tab of OFTP receiver channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/vdaconvertermodule Local Enterprise Bean Vda2xml Use the Move Up button to move module for VDA Converter as first Module. Save the Integration Flow for Partner 1 by pressing save button. ( ) 3.2.5 Creating the Integration Flow for Partner 2 Perform the following steps to create a Partner 2 integration flow. 8. In the Process Integration Designer choose New Integration Flow ( ). 9. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name or the Integration Flow as B2B_OFTPScenario1_Partner2. 10. Choose Next. 11. As Sender Business System select the Business System <SID>_iFlow_FileSystem_OFTP_Partner2 you imported from SLD using the Browse button. 12. As Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 13. In Tab Receiver Systems select the Business Component <SID>_iFlow_FileSystem_OFTP_Partner2 using the input help for the Receiver Name. 14. As Receiver Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 15. Choose Finish. The integration Flow will be displayed in a graphical overview. 3.2.6 Creating Channels for Partner 2 Integration Flow You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. 16. In the graphical editor, click on channel for the sender component. The Details tab for the channel will open. 17. As Channel Name set OFTPSender. 18. As Adapter Type select OFTP B2B TOOLKIT 1.0. 13
19. Select TCP/IP as transport protocol and Message Protocol as OFTP 2.0. 20. Click on Adapter Specific tab and enter the following details on subtab General TCP/IP Settings -> Local hostname You can use fully qualified hostnames or IP addresses of interface the server shall bind to. The address 0.0.0.0 is used for binding to all available interfaces. TCP/IP Settings -> Local Port The TCP port the server shall bind to. Allowed ports are values in [0;65535]. The default ports are 3305 for plain and 6619 for SSL secured OFTP. Please notice that a SAP PI uses many ports by default which may not be assigned. Checkbox -> Use SSL Selected (Determines whether the connection should be encrypted using SSL or not) View Containing SSL Keypair Key store view which contains the public keys Connection Settings > Own Odette ID Own Odette-ID (The Odette ID always starts with the letter O followed by a country-specific ID ( 0013 for Germany), a unique, partner specific part and a part everyone may choose freely e.g. O0013SAPPJ8P2) Connection Settings > Partner Odette ID Partner Odette-ID (e.g. O0013SAPPJ8P1) Connection Settings > Final File Destination (SFIDDEST) Destination SFID as agreed upon with partner Connection Settings > File Originator (SFIDORIG) Originator SFID as agreed upon with partner Connection Settings > Own Password (Receiver) Receiver password (agreed upon by bilateral agreement) Connection Settings > Partner Password (Sender) Sender password (agreed upon by bilateral agreement) File Settings -> Expected Virtual File Dataset Name The expected file name given as regular expression (e.g. ->.*) http://docs.oracle.com/javase/1.4.2/docs/api/java/util/regex/pattern.html Encoding If the incoming file needs to be converted to UTF-8 the original file encoding has to be specified here. (No conversion -> No Encoding) 14
Quality of service Exactly Once (asynchronous) Archiving -> Archive Messages Select Checkbox to archive message Incoming Wired Message Select checkbox and provide location to archive the file (Refer Step 2.2.6 -> 5 for directory location) Payload After Decryption Select checkbox and provide location to archive the file after decryption (Refer Step 2.2.6 -> 5 for directory location) Optional -> Archive Error messages Error Messages can also be archived to get the file in case of erroneous situations. Select checkbox and provide location to archive the file (Refer Step 2.2.6 -> 5 for directory location) 21. Go to Technical settings subtab and enter the following below details Checkbox -> Allow Compression (1.X RLE) Selected - The location can handle OFTP data buffer compression (Compression is only used if supported by both locations) Checkbox -> Version Negotiable This is to allow OFTP 1.x to OFTP 2.0 communication and vice versa Max Credit Count The number of consecutive Data Exchange Buffers sent by the Speaker before it must wait for a Credit (CDT) command from the Listener (default value - 15) Max Exchange Buffer Size The length, in octets, of the largest Data Exchange Buffer that can be accepted by the location. The length includes the command octet but does not include the Stream Transmission Header. After negotiation, the smallest size will be selected. 7. Go to ERP subtab and leave entries as per default values. 8. Go to CMS subtab and enter the following below details KeyStore containing own certificates and keys NWA Key Storage view which contains own certificates and keys KeyStore containing partner certificates NWA Key Storage view which contains partner certificates 15
Checkbox -> Decrypt files Selected (Decrypt the received file. The decryption algorithm has to be set by bilateral agreement) Checkbox -> Verify Signature Verify the signature of the received file Checkbox -> Use Secure Handshake When using secure handshake both sides have to identify themselves before a session can be opened Checkbox -> Use Compression Compresses all files according to the CMS GZIP specification Checkbox -> Force Signed ERP If this option is enabled signed ERPs (end 2 End response) will be sent 22. Click on Module tab of OFTP sender channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/vdaconvertermodule Local Enterprise Bean Vda2xml Use the Move Up button to move module for VDA Converter as first Module. 23. Go back to graphical editor, click on channel for the receiver component. The Details tab for the channel will open. 24. As Channel Name set FileReceiver. 25. As Adapter Type select File SAP BASIS 7.31. 26. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see Error! Reference source not found.). In the case of the receiver communication channel, enter the whole path for the file directory Receiver. Example: C:/<selected path>/b2b/oftp/receiver 27. As File Name set VDA_Output.txt. 28. Click on Module tab of File receiver channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/vdaconvertermodule Local Enterprise Bean Vda2xml Use the Move Up button to move module for VDA Converter as first Module. 29. Save the Integration Flow for Partner 2 by pressing save button. ( ) 3.2.7 Activating the Configuration Objects In the following steps, you save the integration flow with all its objects and activate it for the runtime. 1. Use the Activate entry in the context menu of the integration flow B2B_OFTPScenario1_Partner1 to activate the configuration. 2. Use the Deploy entry in the context menu of the integration flow B2B_OFTPScenario1_Partner1 to deploy it in the runtime. 16
3. Following Step 1 & 2, Activate and Deploy the Integration Flow B2B_OFTPScenario1_Partner2. 4 Variant 2: Partner 1 & Partner 2 via TCP/IP transport with Odette Converter Module using Odette format file This variant enables you to configure and execute message exchange between two Integration Flows acting as two different partners. In Partner1 Integration Flow, File Adapter picks an Odette format file and converts in xml using Odette- XML Converter module within PI Advanced Adapter Engine Extended. On receiver side, OFTP adapter transfers the file to OFTP sender of Partner2 Integration Flow using OFTP protocol which enables secure authentication via Odette ID (SSID), SFID and an additional sender and receiver password authentication. At last, file receiver converts the file back to Odette format and stores it into the relevant directory. 4.1 Design Objects Used 4.2 Configuring the Process Integration Scenario In configuration, you use the design objects in the process integration scenario for the actual system landscape. You have already described the system landscape in the SLD. The communication components defined in this section enables you to address them as senders/receivers of messages from the in the Process Integration Designer. You perform the following configuration steps in the SAP Process Integration Designer for the Advanced Adapter Engine Extended. 4.2.1 Calling the Process Integration Designer First, open the SAP NetWeaver Developer Studio. Set the connection data for accessing the Integration Directory under the menu Process Integration Change Preferences. The connection details to the Advanced Adapter Engine Extended System have to be maintained using URL or AEX-Host and AEX-Port. To call the SAP Process Integration Designer follow the menu path Window Open Perspective Other SAP Process Integration Designer. Logon to the AEX system using the Menu Process Integration Connect providing your user credentials. 4.2.2 Creating the Business Components Perform the following steps to create the Business Component: 1. To create the Business Components, select Systems. Right click and select New Business Components options from the context menu. A Pop-up titled Create Business Components will appear. 2. Enter the name of Business Component as <SID>_iFlow_FileSystem_OFTP_Partner3. <SID> is the system ID of the Advanced Adapter Engine Extended System. 3. Click Finish. Business Component details will be open. 4. Within Sender Interface frame, click on Add. Select XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 5. Now click on Add button within receiver interface frame. Select XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31 6. Click on Save button to submit changes to the above created Business Component. 7. Following the above procedure, create three more business components <SID>_iFlow_FileSystem_OFTP_Partner4 8. Add the service interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31 as Sender and Receiver Interface to the above created Business Components. 4.2.3 Creating the Integration Flow for Partner 1 Perform the following steps to create a Partner 1 integration flow. 17
1. In the Process Integration Designer choose New Integration Flow ( ). 2. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name or the Integration Flow as B2B_OFTPScenario2_Partner1 3. Choose Next. 4. As Sender Business System select the Business System <SID>_iFlow_FileSystem_OFTP_Partner3 you imported from SLD using the Browse button. 5. As Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 6. In Tab Receiver Systems select the Business Component <SID>_iFlow_FileSystem_OFTP_Partner3 using the input help for the Receiver Name. 7. As Receiver Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 8. Choose Finish. The integration Flow will be displayed in a graphical overview. 4.2.4 Creating Channels for Partner 1 Integration Flow You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. 1. In the graphical editor, click on channel for the sender component. The Details tab for the channel will open. 30. As Channel Name set FileSender. 31. As Adapter Type select File, SAP BASIS 7.31. 32. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see Error! Reference source not found.). In the case of the sender communication channel, enter the whole path for the file directory Sender. Example: C:/<selected path>/b2b/oftp/sender 33. As File Name set B2B_Odette.txt. 34. Click on Module tab of File sender channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/odetteconverterrmodule Local Enterprise Bean Odette2xml Use the Move Up button to move module for Odette Converter as first Module. 35. Following the same procedure (see step 1-2), create the communication channel OFTPReceiver of Adapter type OFTP B2B TOOLKIT 1.0 for the receiver Component <SID>_iFlow_FileSystem_OFTP_Partner3. 36. Select TCP/IP as transport protocol and Message Protocol as OFTP 2.0. 37. Click on Adapter Specific tab and enter the following details on subtab General TCP/IP Settings -> Partner host Partners host where OFTP Client should connect. On this variant we use the same system (host name) for both Partners. 18
TCP/IP Settings -> Port Allowed ports are values in [0;65535]. The default ports are 3305 for plain and 6619 for SSL secured OFTP e.g. 3312 Checkbox -> Specify Local Host Selected (option through which the outbound communication can happen) e.g. 0.0.0.0 Checkbox -> Use SSL Selected (Determines whether the connection should be encrypted using SSL or not) Verify hostname Selected. Verifies the hostname from the SSL certificate. The CN value inside the certificate should match the actual host name. Use client authentication Selected View Containing Trusted Certificates Key storage view which contains the trusted certificates (OdetteCertificateExchangeProvider) Connection Settings > Own Odette ID Own Odette-ID (The Odette ID always starts with the letter O followed by a country-specific ID ( 0013 for Germany), a unique, partner specific part (e.g. SID), and a part everyone may choose freely e.g. O0013SAPPJ8P1) Connection Settings > Partner Odette ID Partner Odette-ID (e.g. O0013SAPPJ8P2) Connection Settings > File Originator (SFIDORIG) Originator SFID as agreed upon with partner e.g. O0013SAPPJ8ORI Connection Settings > Final File Destination (SFIDDEST) Destination SFID as agreed upon with partner e.g. O0013SAPPJ8DES Connection Settings > Own Password (Sender) Sender password (agreed upon by bilateral agreement) e.g. PassSender Connection Settings > Partner Password (Receiver) Receiver password (agreed upon by bilateral agreement) e.g. PassReceiver File Settings -> Outgoing Virtual File Dataset Name The dataset name of the virtual file which is about to be transferred (e.g. Outfile) 19
File format The format which the file is encoded. Select Text Encoding ISO-8859-1 Description The description of the virtual file being transferred 38. Go to Technical settings subtab and enter the following below details Checkbox -> Allow Compression (1.X RLE) Selected - The location can handle OFTP data buffer compression (Compression is only used if supported by both locations) Checkbox -> Version Negotiable Unselected Max Credit Count The number of consecutive Data Exchange Buffers sent by the Speaker before it must wait for a Credit (CDT) command from the Listener (default value - 15) e.g. 15 Max Exchange Buffer Size The length, in octets, of the largest Data Exchange Buffer that can be accepted by the location. The length includes the command octet but does not include the Stream Transmission Header. After negotiation, the smallest size will be selected. e.g. 128 39. Go to CMS subtab and enter the following below details KeyStore containing own certificates and keys NWA Key Storage view which contains own certificates and keys e.g. OWN_KEYS_P1 KeyStore containing partner certificates NWA Key Storage view which contains partner certificates e.g. PARTNER_KEYS_P1 Checkbox -> Encrypt files Selected (Using this option all files going to be encrypted before being sent. The encryption algorithm has to be set by bilateral agreement) Encryption Algorithm 3DES (Triple Data Encryption Standard) 20
Checkbox -> Sign files Sign the file with MD5 (Message Digest Algorithm 5) Use Secure Handshake Selected. Authentication Challenge Indicator Use Compression Selected. File Compression indicator Force Signed ERP Selected. Mandatory of singed EERP/NERP 40. Click on Module tab of OFTP receiver channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/odetteconverterrmodule Local Enterprise Bean Xml2Odette Use the Move Up button to move module for Odette Converter as first Module. Save the Integration Flow for Partner 1 by pressing save button. ( ) 4.2.5 Creating the Integration Flow for Partner 2 Perform the following steps to create a Partner 2 integration flow. 1. In the Process Integration Designer choose New Integration Flow ( ). 41. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name or the Integration Flow as B2B_OFTPScenario2_Partner2. 42. Choose Next. 43. As Sender Business System select the Business System <SID>_iFlow_FileSystem_OFTP_Partner4 you imported from SLD using the Browse button. 44. As Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 45. In Tab Receiver Systems select the Business Component <SID>_iFlow_FileSystem_OFTP_Partner4 using the input help for the Receiver Name. 46. As Receiver Interface select interface XiPatternInterface1 of namespace http://sap.com/xi/xi/system/patterns within SWCV SAP BASIS 7.31. 47. Choose Finish. The integration Flow will be displayed in a graphical overview. 4.2.6 Creating Channels for Partner 2 Integration Flow You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. 1. In the graphical editor, click on channel for the sender component. The Details tab for the channel will open. 2. As Channel Name set OFTPSender. 3. As Adapter Type select OFTP B2B TOOLKIT 1.0. 21
4. Select TCP/IP as transport protocol and Message Protocol as OFTP 2.0. 5. Click on Adapter Specific tab and enter the following details on subtab General TCP/IP Settings -> Local hostname You can use fully qualified hostnames or IP addresses of interface the server shall bind to. The address 0.0.0.0 is used for binding to all available interfaces. TCP/IP Settings -> Local Port The TCP port the server shall bind to. Allowed ports are values in [0;65535]. The default ports are 3305 for plain and 6619 for SSL secured OFTP. Please notice that a SAP PI uses many ports by default which may not be assigned. e.g. 3312 Checkbox -> Use SSL Selected (Determines whether the connection should be encrypted using SSL or not) Checkbox -> Use client authentication Selected View Containing SSL Keypair Key storage view which contains the public keys e.g. OWN_KEYS_P2 View containing trusted certificates e.g. OdetteCertificateExchangeProvider Connection Settings > Own Odette ID Own Odette-ID (The Odette ID always starts with the letter O followed by a country-specific ID ( 0013 for Germany), a unique, partner specific part and a part everyone may choose freely e.g. O0013SAPPJ8P2) O0013SAPPJ8PAR Connection Settings > Partner Odette ID Partner Odette-ID O0013SAPPJ8OWN Connection Settings > Final File Destination (SFIDDEST) Destination SFID as agreed upon with partner e.g. O0013SAPPJ8DES Connection Settings > File Originator (SFIDORIG) Originator SFID as agreed upon with partner e.g. O0013SAPPJ8ORI Connection Settings > Own Password (Receiver) Receiver password (agreed upon by bilateral agreement) e.g. PassReceiver 22
Connection Settings > Partner Password (Sender) Sender password (agreed upon by bilateral agreement) e.g. PassSender File Settings -> Expected Virtual File Dataset Name The expected file name given as regular expression (e.g. ->.*) e.g. outfile Encoding If the incoming file needs to be converted to UTF-8 the original file encoding has to be specified here. Select ISO-8859-1 Quality of service Best Effort (synchronous) 6. Go to Technical settings subtab and enter the following below details Checkbox -> Allow Compression (1.X RLE) Selected - The location can handle OFTP data buffer compression (Compression is only used if supported by both locations) Checkbox -> Version Negotiable Not selected. If no OFTP 2.0 security features are enabled, the version is negotiable with the partner Max Credit Count The number of consecutive Data Exchange Buffers sent by the Speaker before it must wait for a Credit (CDT) command from the Listener (default value - 15) e.g. 15 Max Exchange Buffer Size The length, in octets, of the largest Data Exchange Buffer that can be accepted by the location. The length includes the command octet but does not include the Stream Transmission Header. After negotiation, the smallest size will be selected. e.g. 128 7. Go to CMS subtab and enter the following below details KeyStore containing own certificates and keys NWA Key Storage view which contains own certificates and keys e.g. OWN_KEYS_P2 KeyStore containing partner NWA Key Storage view which contains partner certificates 23
certificates e.g. PARTNER_KEYS_P2 Checkbox -> Decrypt files Selected (Decrypt the received file. The decryption algorithm has to be set by bilateral agreement) Checkbox -> Verify Signature Selected. Verify the signature of the received file Checkbox -> Use Secure Handshake Selected. When using secure handshake both sides have to identify themselves before a session can be opened Checkbox -> Use Compression Selected. Compresses all files according to the CMS GZIP specification Checkbox -> Force Signed ERP Selected. If this option is enabled signed EERPs will be sent 8. Click on Module tab of OFTP receiver channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/odetteconverterrmodule Local Enterprise Bean Odette2xml Use the Move Up button to move module for Odette Converter as first Module. 9. Go back to graphical editor, click on channel for the receiver component. The Details tab for the channel will open. 10. As Channel Name set FileReceiver. 11. As Adapter Type select File SAP BASIS 7.31. 12. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see Error! Reference source not found.). In the case of the receiver communication channel, enter the whole path for the file directory Receiver. Example: C:/<selected path>/b2b/oftp/receiver 13. As File Name set Odette_Output.txt. 14. Click on Module tab of OFTP receiver channel. Enter the following below details within Processing Sequence table. Module Name Type Module Key localejbs/odetteconverterrmodule Local Enterprise Bean Odette2xml Use the Move Up button to move module for Odette Converter as first Module. 15. Save the Integration Flow for Partner 1 by pressing save button. ( ) 4.2.7 Activating the Configuration Objects In the following steps, you save the integration flow with all its objects and activate it for the runtime. 1. Use the Activate entry in the context menu of the integration flow B2B_OFTPScenario2_Partner1 to activate the configuration. 24