BizTalk Server Adapters

Transcription

1 BizTalk Server Adapters Adapters included with BizTalk Server 2010 The following adapters are included with BizTalk Server 2010 licenses. Adapter Description Supported Editions SAP Siebel ebusiness Applications Oracle ebusiness Suite Supports execution of BAPIs, RFCs, and trfcs, data exchange using IDOCs, and receiving events from SAP with a generic RFC Server. The SAP adapter has received "Certified for SAP NetWeaver" status from SAP. Provides access to Siebel ebusiness Applications via Business Objects, Business Components, and Business Services. Provides access to Oracle ebusiness Suite applications. Based on ADO.NET. Provides access to Oracle Database tables, views, stored procedures, SAP R/3 4.x and R/ (Enterprise), SAP ECC 6.0, and SAP , 7.7, 7.8, 8.0 ODP.NET , Oracle EBS , and 12.1 Oracle Database functions, and PL/SQL packages. Timed polling is also provided, Oracle 9i ( ), 10g allowing applications to periodically look for changes in the database. ( & ) SQL Server WCF LOB Adapter SDK Microsoft Dynamics CRM 4.0 This adapter is based on ADO.NET. Provides access to SQL Server databases Provides a simple programming model for developing adapters that are based on Windows Communication Foundation. This is a separate download available to everyone using the.net Framework 3.0. The Microsoft BizTalk Server Adapter for Microsoft Dynamics CRM 4.0 enables integration between Microsoft Dynamics CRM 4.0 and other business applications. 2000, 2005, 2008, and 2008 R Microsoft Dynamics CRM 4.0 PeopleSoft Enterprise JD Edwards OneWorld XE JD Edwards EnterpriseOne Note - This adapter is only available as a separate download. Enables exchange of Business Function messages between BizTalk Server and a PeopleSoft Enterprise system. Enables exchange of Business Function messages between BizTalk Server and a JD Edwards EnterpriseOne system. Enables exchange of Business Function messages between BizTalk Server and a JD Edwards EnterpriseOne system. PeopleTools Versions , 8.43, 8.45, 8.46, 8.47, 8.48, 8.49 and 9.0 B w/ SP23 and JDE 8.0 (B ) 8.10, 8.11, 8.12 with Tools Release 8.93, 8.94, 8.95, 8.96, 8.97, and 9.0 TIBCO Rendezvous Enables exchange of XML and binary data format messages between 7.3, 7.4.5, 7.5.4, 8.1.1

2 TIBCO Enterprise Message Service Host Applications BizTalk Server and TIBCO Rendezvous. Enables exchange of XML and binary data format messages between BizTalk Server and a TIBCO EMS server providing a tightly integrated and reliable application infrastructure. Enables data exchange between BizTalk Server and IBM mainframe zseries (CICS and IMS) and midrange iseries (AS/400) server programs. 4.2, 4.4.3, 5.0 IBM CICS for z/os V3.1, V3.2 and V4.1 IBM IMS V10 and IMS V11 IBM i5/os V5R4 and V6R1 IBM DB2 for z/os V8.1 and DB2 for z/os V9.1 IBM DB2 Host Files WebSphere MQ (Client Based) WebSphere MQ MSMQ FILE Enables reading and writing information from and to IBM mainframe DB2 for z/os, IBM midrange DB2/400, and IBM DB2 Universal Database for open platforms (AIX, Linux, Solaris, and Windows). Enables data exchange between BizTalk Server and IBM mainframe zseries VSAM datasets and IBM midrange iseries AS/400 physical files. Enables exchange of messages between BizTalk Server and IBM WebSphere MQ using the WebSphere MQ Base Client (nontransactional) or WebSphere MQ Transaction Extended Client APIs. Enables exchange of messages between BizTalk Server and IBM WebSphere MQ. Enables sending and receiving messages to and from Microsoft Message Queue (MSMQ). Enables reading from and writing to files in the Microsoft Windows file system. IBM DB2 for i5/os V5R4 and V6R1 IBM DB2 for Windows, AIX, HP-UX, Solaris, Linux V9.1, V9.5, V9.7 IBM DFSMS DFM z/os V1.9, V1.10 and V1.11 IBM i5/os V5R4 and V6R1 IBM WebSphere MQ Client 6.0 with Fix Pack or 7.0 with Fix Pack IBM WebSphere MQ Server 6.0 with Fix Pack or 7.0 with Fix Pack and 3.0 FTP Enables exchange of files between BizTalk Server and FTP servers. FTPs HTTP Enables secure exchange of files between BizTalk Server and FTP servers, fully supporting RFC4217. Enables sending and receiving information by using HTTP. The BizTalk Server engine exposes one or more URLs to enable other

3 POP3 SMTP SOAP Windows Communication Foundation (WCF) SharePoint applications to send data to it, and it can use this adapter to send data to other URLs. Enables receiving messages from a POP3 mailbox into BizTalk Server by using the POP3 protocol. Enables sending messages between BizTalk Server and an SMTP gateway by using Simple Mail Transfer Protocol (SMTP). Enables sending and receiving messages by using SOAP over HTTP enabling BizTalk Server to interact in a Web services world. Includes seven adapters and wizards that enable easy communication to and from BizTalk Server and Web services-based applications via the Windows Communication Foundation (WCF). Enables the exchange of XML and binary messages between BizTalk Server and SharePoint document libraries..net Framework 3.5 Windows SharePoint Services 3.0, SharePoint Foundation 2010

4 Certificates that BizTalk Server Uses for Signed Messages 0 out of 1 rated this helpful - Rate this topic BizTalk Server supports signing outbound messages and signature verification for inbound Secure Multipurpose Internet Mail Extensions (S/MIME) messages. BizTalk Server uses S/MIME versions 2 and 3 to sign outbound messages and to validate the signature of inbound messages. Similarly, you can configure BizTalk Server to sign and then encrypt the messages it sends to its partners. BizTalk Server supports the SHA-1 and MD5 signing algorithms for verifying digital signatures. BizTalk Server uses the SHA-1 signing algorithm to sign outbound messages. The key exchange systems supported by BizTalk Server for signature keys are the Rivest-Shamir- Adleman (RSA) algorithms and the Digital Signature Standard (DSS). BizTalk Server does not support the Advanced Encryption Standard (AES) exchange system for signature keys. The signing certificate supported by BizTalk Server is x.509 version 3. The following figure shows the message flow when BizTalk Server receives a digitally signed message and optionally uses the signature to resolve the partner identity to a party in the BizTalk Server environment. The message flow when BizTalk Server receives a digitally signed message is as follows: 1. A partner sends a message to BizTalk Server. The partner signs the message with its private key certificate.

5 2. The appropriate BizTalk Server receive handler receives the message. 3. During the execution of the receive pipeline, the MIME/SMIME Decoder pipeline component verifies the digital signature by using the partner's public key. 4. If party resolution component is configured, the partner's public key certificate is used to identify the party in the BizTalk Server system during the execution of the receive pipeline party resolution component. 5. Additional processing occurs. The following figure shows the message flow when BizTalk Server sends a digitally signed message. The message flow when BizTalk Server sends a digitally signed message to a partner is as follows: 1. The appropriate BizTalk Server send handler sends a message to the partner. 2. During the execution of the send pipeline, the MIME/SMIME Encoder pipeline component signs the message by using the BizTalk Server private key. 3. The partner receives the message from BizTalk Server. The partner uses the BizTalk Server public key to verify the digital signature. BizTalk Server verifies the validity of the certificates associated with the incoming signed messages by validating the certificate authority (CA) trust chain for the certificate and by verifying that the certificate has not expired. The process of validating the CA trust chain involves traversing the chain of trust on certificates

6 until a root certificate authority is reached. This validates that the certificate used to sign a message is indeed from the identified party. This validation occurs at runtime for each and every signed message. In addition, BizTalk Server can verify that the certificate authority has not revoked the certificate used to sign or encrypt the message. To do this, you must download the certificate revocation list (CRL) from the certificate authority and install it using Windows Explorer. For more information about how to validate a certificate, see How to Configure the MIME/SMIME Decoder Pipeline Component

7 Certificates that BizTalk Server Uses for Encrypted Messages This topic has not yet been rated - Rate this topic BizTalk Server supports public key encryption of outbound messages and decryption of inbound messages based on Secure Multipurpose Internet Mail Extensions (S/MIME). BizTalk Server uses S/MIME version 3 for encryption of outbound messages, and S/MIME versions 2 and 3 for decryption of inbound messages. BizTalk Server supports RSA and Diffie Hellman encryption certificates. BizTalk Server supports Data Encryption Standard (DES), 3DES, and RC2 encryption algorithms. The following figure shows the message flow when BizTalk Server receives an encrypted message. The message flow when BizTalk Server receives an encrypted message is as follows: 1. A partner sends a message to BizTalk Server. The partner encrypts the message with the BizTalk Server public key. 2. The appropriate BizTalk Server receive handler receives the message. 3. During the receive pipeline execution, the MIME/SMIME Decoder pipeline component decrypts the message by using the BizTalk Server private key.

8 Note For pipeline decryption to succeed on an IIS 7.0 computer, ensure that the account for the IIS application pool and the account used by the host instance associated with the receive handler are the same and that this account is a member of the <machinename>\iis_wpg group. For more information on setting IIS process identity for IIS 7.0 see Guidelines for Resolving IIS Permissions Problems. These processes must run under the same account to ensure that the account profile is loaded which in turns loads the registry keys required to perform decryption in the pipeline. For performance reasons, IIS 7.0 does not load the account profile when starting the associated w3wp.exe process so the BizTalk host instance must be configured with the same account so that BizTalk will load the account profile and registry keys. 4. Additional processing occurs. The following figure shows the message flow when BizTalk Server sends an encrypted message. The message flow when BizTalk Server sends an encrypted message to a partner is as follows: 1. The appropriate BizTalk Server send handler sends a message to the partner. 2. During the send pipeline execution, the MIME/SMIME Encoder pipeline component encrypts the message by using the partner's public key.

9 3. The partner receives the message from BizTalk Server. The partner uses its private key to decrypt the message.

10 Övrigt Eskilstuna Kommun har förutom de BizTalk Server Adapters som ingår i Biztalk 2010 tillgång till SFTP. För signering av filer har Eskilstuna Kommun förutom det som ingår i Biztalk 2010 tillgång till HMAC256