470 likes | 613 Views
Hands-On Training. Larry Gregory Tony Sukiennick. Day 1 Overview Installation Orchestration Orchestration Samples Messaging XML Tools Samples PO Approval Lab. Day 2 Advanced BTO Scripting and WMI .Net Server Integration Lessons Learned Advanced BTM Deployment The Contest
E N D
Hands-On Training Larry Gregory Tony Sukiennick
Day 1 Overview Installation Orchestration Orchestration Samples Messaging XML Tools Samples PO Approval Lab Day 2 Advanced BTO Scripting and WMI .Net Server Integration Lessons Learned Advanced BTM Deployment The Contest EDI Primer and Lab Class Agenda
Real Life Scenario:4 Day Proof of Concept cXML/File NSF/API Notes Ariba EAI EDI/MQ EDI center(MQ Series) CSV/File SAP iDOC/DCOM EDI/MQ
The Details XML CXMLLib Parse BTS MSMQ BTO CXMLLib GetFilterValue SE? MSMQ BTS BTS Notes NSF EDI
Observations/Gotchas • Docspecs and mapping take a long time without data experts nearby • Preparsing required for some documents • Need access to system administrators early to minimize configuration delays • SAP DCOM Connector can push and inquiry but not be called by SAP • BizTalk AIC only implements a push mechanism • Don’t uninstall MSMQ the night before demo • Compaq, Viewlocity, and Neon claim to provide BizTalk connectors
Other Lessons Learned • Start small • Find a standard • Provide base training • Incorporate IT/business data experts • Data assembly is an organizational puzzle • Adequate lab environment • Sophisticated test harness • Start testing with Partner early • Identify a vested interest • Scripting BTM setup – saves time • Add debug actions when modeling
Overview • Encryption – Prevents documents from being viewed by unauthorized individuals • Signing – Ensures that a document is authentic and unaltered
Symmetrical Encryption • Encryption may be performed using either the public key or private key • Only the opposite key may be used to decrypt a message • The public key cannot be used to decrypt a document encrypted with the public key
Encryption • Source must have access to the destination’s digital certificate containing the public key • Source encrypts the message using the destination’s public key • BizTalk Server 2000 creates an S/MIME document with the encrypted message as the body of the document
Decryption • Destination must have access to their own digital certificate containing the matching private key • PKI searches the certificate store automatically to locate the appropriate certificate • The destination’s private key is used to decrypt the document
Signing • The document is run through a hash algorithm • Source uses their own private key to encrypt the signature containing the hash value • BizTalk Server 2000 produces an S/MIME document with the message and signature as an attachment
Signature Verification • Destination must have access to a digital certificate with the source’s public key • The source’s public key is used to decrypt the signature • The message is run through the same hash algorithm • The hash value is compared to the hash value stored in the signature
Certificates MMC Snap-in Certificates with private keys (Signing & Decryption) Root CA certificates Certificates with public keys only (Encryption)
Channel Configuring Channels and Ports Information about the Source Information about the Destination S/MIME Document My Document Port Signature Encryption
Channel ConfigurationSpecifying a Signature Select the certificate Check to enable signature
Port ConfigurationSpecifying Encryption & Signature Select S/MIME Select a certificate Select S/MIME
Channel ConfigurationSpecifying Decryption & Signature Verification Check to verify decryption Select the destination’s certificate with the private key Check to verify signature Select the source’s certificate with the public key
Lab Overview • Add encryption and signing to the existing PO Approval scenario Home.com Signed response Encrypted and signed PO Secure Email Buyer.com Approver.com
Other Thoughts… • Self Routing Documents
Client Deployment Options SQL Port HTTP MSMQ SMTP HTTP Web Server SQL Server BizTalk Server
SQL Server • InterchangeBTM – least activity • InterchangeSQ – large amount of both reads and writes across network • InterchangeDTA – lot of writes but less reads across network • Orchestration Persistence – local writes and reads
BT Admin Optimization • Set MO cache refresh interval • Prioritize parsers • Disable document tracking • Consider dedicated receive servers • Adjust number of receive threads • Adjust number of worker threads
Registry settings OptimizationHKLM\System\Current Control Set\Services\BTSSVC • Turn off schema validation • NoValidation • Set parser refresh interval • ParserRefreshInterval (Default = 60 sec) • Set the size of MO cache • CacheSize (Default = 20 objects) • Set MSMQ receive batch size • BatchSize (Default = 20)
Monitoring Performance • Messaging performance counters, e.g. • docs received / sec • synch submitted /sec • parsed / sec • Other performance counters • MSMQ, HTTP • CPU, memory, network • AppCenter Health Monitors
Other Tools • Monitoring Tool • monitors state and performance • Available soon after RTM • Central view on entire system • Great for debugging and detecting bottlenecks • Configuration Utility and BizPort • XLANG Monitor
EDI Primer Larry Gregory
Intro to EDI X12 • ISA Interchange Control Header • GS Functional Group Control Header • ST Transaction Set Header • SE Transaction Set Trailer • GE Functional Group Control Trailer • IEA Interchange Control Trailer ISA|00| |00| |ZZ|THEMDATEA |ZZ|USDATE00A |000321|0450|U|00401|000000071|0|P|>~GS|FA|SENDDATE94|RECDATE60|20000321|0450|27|X|004010~ST|997|0001~AK1|IN|80~AK2|810|0001~AK5|A~AK9|A|1|1|1~SE|6|0001~GE|1|27~IEA|1|000000071~
Delimiters Element (Record) Separator Component Element (Field) Separator ISA|00| |00| |ZZ|THEMDATEA |ZZ|USDATE00A |000321|0450|U|00401|000000071|0|P|>~GS|FA|SENDDATE94|RECDATE60|20000321|0450|27|X|004010~ST|997|0001~AK1|IN|80~AK2|810|0001~AK5|A~AK9|A|1|1|1~SE|6|0001~GE|1|27~IEA|1|000000071~ Segment (Segment) Terminator
Relevant Routing Parameters Specified to BTS as Organization Identifiers • Interchange ID Qualifier (ZZ) • Interchange Sender ID (THEMDATEA) • Interchange Receiver ID (USDATE00A) • Functional_Identifier (FA) • Application_Sender_Code (SENDDATE94) • Application_Receiver_Code (RECDATE60) • Standards_Version (004010) • Transaction Set Identifier Code (997) Specified to BTS as Document Selection Criteria ISA|00| |00| |ZZ|THEMDATEA |ZZ|USDATE00A |000321|0450|U|00401|000000071|0|P|>~GS|FA|SENDDATE94|RECDATE60|20000321|0450|27|X|004010~ST|997|0001~AK1|IN|80~AK2|810|0001~AK5|A~AK9|A|1|1|1~SE|6|0001~GE|1|27~IEA|1|000000071~
Document Definition • Inbound: locates document definition for EDI documents • Outbound: creates functional group fields in envelope header
Demo: EDI to XML • Steps to Convert EDI X12 to XML • Create Organizations • Create Document Definitions • Create Map • Create Port • Create Channel • Create Receive Function to Test
Lab EDI Conversion
Intro to EDIFACT • EDIFACT Service Segments • UNA =Service String advice • UNB =Interchange header • UNG =Group header • UNH =Message header
Relevant EDIFACT Parameters Specified to BTS as Organization Identifiers • Identification code qualifier (ZZZ) • Interchange sender identification (XYZ.ORG) • Interchange recipient identification (ABC.ORG) • Functional_identifier (INVOIC) • Application_sender_code (XYZ.ORG) • Application_receiver_code (ABC.ORG) • Standards_version_type (D) • Standards_version_value (96A) Specified to BTS as Document Selection Criteria UNB+UNOA:1+XYZ.ORG:ZZZ+ABC.ORG:ZZZ+000504:2249+51++++++1' UNH+1+INVOIC:D:96A:UN' BGM+380+2000.021994' DTM+137:20000504:102’
Thanks for Attending! • Product design feedback to larrygr • Available for closing big dot-com opportunities • Next training is 12/14-15 • www.UWannaDotCom.Com