BEA WebLogic Integration. Using EDI with WebLogic Integration

Transcription

1 BEA WebLogic Itegratio Usig EDI with WebLogic Itegratio Versio 2.1 Documet Date: October 2001 Revised: November 2, 2001

2 Copyright Copyright 2001 BEA Systems, Ic. All Rights Reserved. Restricted Rights Leged This software ad documetatio is subject to ad made available oly pursuat to the terms of the BEA Systems Licese Agreemet ad may be used or copied oly i accordace with the terms of that agreemet. It is agaist the law to copy the software except as specifically allowed i the agreemet. This documet may ot, i whole or i part, be copied photocopied, reproduced, traslated, or reduced to ay electroic medium or machie readable form without prior coset, i writig, from BEA Systems, Ic. Use, duplicatio or disclosure by the U.S. Govermet is subject to restrictios set forth i the BEA Systems Licese Agreemet ad i subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR ; subparagraph (c)(1)(ii) of the Rights i Techical Data ad Computer Software clause at DFARS , subparagraph (d) of the Commercial Computer Software--Licesig clause at NASA FAR supplemet ; or their equivalet. Iformatio i this documet is subject to chage without otice ad does ot represet a commitmet o the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. Trademarks or Service Marks BEA, Jolt, Tuxedo, ad WebLogic are registered trademarks of BEA Systems, Ic. BEA Builder, BEA Campaig Maager for WebLogic, BEA elik, BEA Maager, BEA WebLogic Commerce Server, BEA WebLogic E-Busiess Platform, BEA WebLogic Eterprise, BEA WebLogic Express, BEA WebLogic Itegratio, BEA WebLogic Persoalizatio Server, BEA WebLogic Portal, BEA WebLogic Server ad How Busiess Becomes E-Busiess are trademarks of BEA Systems, Ic. All other trademarks are the property of their respective compaies. Usig EDI with WebLogic Itegratio Part Number Date Software Versio N/A October 2001 Revised: November 2,

3 Cotets 1. EDI Backgroud What Is EDI? Architecture Overview Message Structure Differeces with Other E-Commerce Stadards EDI Stadards X EDIFACT TRADACOMS BEA WebLogic EDI Itegratio Architecture BEA WebLogic Adapter for Power.Eterprise! Power.Eterprise! Software Architecture EDI Itegratio Architecture Power.Eterprise! Architecture Feature Overview Supported Stadards Limitatios Power.Map! Creatig ad Maitaiig Maps Creatig ad Maitaiig Documets Power.Maager! Tradig Parter Maiteace Coectios Exchage Profiles Documet Trackig Usig EDI with WebLogic Itegratio iii

4 Admiistratio VAN ad Network Coectivity BEA WebLogic Adapter for Power.Eterprise! 3.0 Overview of Applicatio Itegratio Applicatio Views Cofigurig the BEA WebLogic Adapter for Power.Eterprise! Evets Cofigurig Evets Testig a Evet Services Cofigurig Services Testig a Service Usig the Adapter Plug-I to the BEA WebLogic Itegratio Studio Deployig a Adapter i a New WebLogic Itegratio Domai Exceptio Hadlig Cofigurig Power.Eterprise! Istallig Power.Eterprise! Gettig Liceses Istallig the Power.Server! Istallig the Power.Cliet! Coectig to Get2Coect.Net Istallig Cleo A Dowloadig Software Updates Updatig EDI Documet Descriptios Coectig to a Server for the First Time Cofigurig Power.Eterprise! Cofigurig Tradig Parters Mappig XML ad EDI Data Coectios ad VAN Coectivity Creatig RMI Coectios Creatig Tradig Parter Coectios Cofigurig Exchage Profiles iv Usig EDI with WebLogic Itegratio

5 5. Cofigurig EDI Itegratio Geeral Cofiguratio Cofigure Tradig Parters Cofigure VAN/Tradig Parter Coectivity Cofigurig EDI Itegratio to Receive a EDI Documet Pre-Plaig Withi Power.Eterprise! Withi BEA WebLogic Itegratio Cofigurig EDI Itegratio to Sed a EDI Documet Pre-Plaig Withi Power.Eterprise! Withi BEA WebLogic Itegratio EDI Sample Sample Overview Settig up ad Ruig the Sample Prerequisites Hardware ad OS Requiremets Cofigurig the EDI Sample Step 1: Start Power.Server! Step 2: Start Power.Maager! ad Cofigure Parters Step 3: Start Power.Map! ad Load Maps ad Adapters Step 4: Set Up the Coectios Step 5: Set Up the Exchage Profiles Step 6: Set Up the Workflow Step 7: Deploy the Applicatio View Step 8: Ru the Sample Power.Eterprise! Tuig Guide Tuig the Java Virtual Machie Tuig the Database Tuig Power.Server! HTTP ad HTTPS Server Cofiguratio Usig EDI with WebLogic Itegratio v

6 vi Usig EDI with WebLogic Itegratio

7 About This Documet This documet describes Electroic Data Iterchage (EDI) ad explais how to use the BEA WebLogic Adapter for Power.Eterprise! 3.0 to itercoect with your tradig parters usig EDI i the BEA WebLogic eviromet. This documet icludes the followig topics: Chapter 1, EDI Backgroud, provides backgroud iformatio about EDI systems ad stadards. Chapter 2, Architecture, describes the structure of EDI Itegratio ad its compoet parts. Chapter 3, BEA WebLogic Adapter for Power.Eterprise! 3.0, explais how to istall ad cofigure this product. Chapter 4, Cofigurig Power.Eterprise!. explais how you eed to cofigure Power.Eterprise! to iteroperate with BEA WebLogic Itegratio ad the BEA WebLogic Adapter for Power.Eterprise! 3.0. Chapter 5, Cofigurig EDI Itegratio, explais the ed-to-ed cofiguratio requiremets of EDI Itegratio. Chapter 6, EDI Sample, walks you through the cofiguratio ad use of a example sceario i which EDI is used to support a simple purchase order busiess process. Chapter 7, Power.Eterprise! Tuig Guide. explais how to tue the Power.Eterprise! software for improved performace i your deploymet eviromet. Usig EDI with WebLogic Itegratio vii

8 What You Need to Kow This guide is writte for busiess aalysts ad system admiistrators developig ad implemetig EDI itegratio. We assume that you have a basic uderstadig of EDI ad etworkig cocepts, ad that you are familiar with the WebLogic Itegratio eviromet e-docs Web Site BEA product documetatio is available o the BEA corporate Web site. From the BEA Home page, click o Product Documetatio or go directly to the e-docs Product Documetatio page at How to Prit the Documet You ca prit a copy of this documet from a Web browser, oe file at a time, by usig the File Prit optio o your Web browser. A PDF versio of this documet is available o the WebLogic Itegratio documetatio Home page o the e-docs Web site (ad also o the documetatio CD). You ca ope the PDF i Adobe Acrobat Reader ad prit the etire documet (or a portio of it) i book format. To access the PDFs, ope the WebLogic Itegratio documetatio Home page, click the PDF files butto ad select the documet you wat to prit. If you do ot have the Adobe Acrobat Reader, you ca get it for free from the Adobe Web site at viii Usig EDI with WebLogic Itegratio

9 Related Iformatio For geeral iformatio about EDI ad EDI stadards, see the followig Web sites: Accredited Stadards Committee X12 Web site at UN EDIFACT Web site at Cotact Us! Your feedback o the BEA WebLogic Itegratio documetatio is importat to us. Sed us at docsupport@bea.com if you have questios or commets. Your commets will be reviewed directly by the BEA professioals who create ad update the WebLogic Itegratio documetatio. I your message, please idicate that you are usig the documetatio for the BEA WebLogic Itegratio 2.1 release. If you have ay questios about this versio of BEA WebLogic Itegratio, or if you have problems istallig ad ruig BEA WebLogic Itegratio, cotact BEA Customer Support through BEA WebSupport at You ca also cotact Customer Support by usig the cotact iformatio provided o the Customer Support Card, which is icluded i the product package. Whe cotactig Customer Support, be prepared to provide the followig iformatio: Your ame, address, phoe umber, ad fax umber Your compay ame ad compay address Your machie type ad authorizatio codes The ame ad versio of the product you are usig A descriptio of the problem ad the cotet of pertiet error messages Usig EDI with WebLogic Itegratio ix

10 Documetatio Covetios The followig documetatio covetios are used throughout this documet. Covetio boldface text Ctrl+Tab italics moospace text moospace boldface text moospace italic text UPPERCASE TEXT Item Idicates terms defied i the glossary. Idicates that you must press two or more keys simultaeously. Idicates emphasis or book titles. Idicates code samples, commads ad their optios, data structures ad their members, data types, directories, ad file ames ad their extesios. Moospace text also idicates text that you must eter from the keyboard. Examples: #iclude <iostream.h> void mai ( ) the poiter psz chmod u+w * \tux\data\ap.doc tux.doc BITMAP float Idetifies sigificat words i code. Example: void commit ( ) Idetifies variables i code. Example: Strig expr Idicates device ames, eviromet variables, ad logical operators. Examples: LPT1 SIGNON OR x Usig EDI with WebLogic Itegratio

11 Covetio Item { } Idicates a set of choices i a sytax lie. The braces themselves should ever be typed. [ ] Idicates optioal items i a sytax lie. The brackets themselves should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list]... Separates mutually exclusive choices i a sytax lie. The symbol itself should ever be typed.... Idicates oe of the followig i a commad lie: That a argumet ca be repeated several times i a commad lie That the statemet omits additioal optioal argumets That you ca eter additioal parameters, values, or other iformatio The ellipsis itself should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list] Idicates the omissio of items from a code example or from a sytax lie. The vertical ellipsis itself should ever be typed. Usig EDI with WebLogic Itegratio xi

12 xii Usig EDI with WebLogic Itegratio

13 CHAPTER 1 EDI Backgroud This sectio presets a overview of Electroic Data Iterchage (EDI), the various EDI stadards, ad BEA s EDI Itegratio. It icludes the followig topics: What Is EDI? EDI Stadards BEA WebLogic EDI Itegratio Architecture What Is EDI? Electroic Data Iterchage (EDI) is a set of commo data format stadards developed i the U.S. ad Wester Europe i the late 1970s.The goal of the America Natioal Stadards Istitute (ANSI), which sposored the iitial creatio of what became the X12 set of EDI stadards, was to establish a group of atioally recogized data formats that: Were hardware idepedet Were uambiguous, such that they could be used by all tradig parters Reduced the amout of labor-itesive work required to exchage data (for example, by elimiatig the eed for data re-etry Allowed the seder of the data to cotrol the exchage, ad to kow whether ad whe the recipiet received the trasactio Usig EDI with WebLogic Itegratio 1-1

14 1 EDI Backgroud After sposorig the iitial defiitio of the stadards, ANSI created the Accredited Stadards Committee (ASC) to maitai ad develop the X12 stadard. The resultig X12 stadards defie the data formats ad ecodig rules used for a wide variety of busiess trasactios, icludig order placemet ad processig, shippig ad receivig, ivoicig, paymet, ad may more. To create a sigle iteratioal EDI stadard, the Uited Natios/ Ecoomic Commissio for Europe (UN/ECE) Workig Party o Facilitatio of Iteratioal Trade Procedures created the UN/EDIFACT family of stadards. The EDIFACT sytax was adopted by the Iteratioal Stadards Orgaizatio (ISO) i The X12 ad EDIFACT stadards provide equivalet fuctioality. The X12 stadards are older ad more mature; they provide fuctioality ot yet available i EDIFACT. Much of this uavailable fuctioality is, however, uder developmet for the EDIFACT stadards. The differeces betwee X12 ad EDIFACT arise primarily from their uderlyig data structures. (For example, data elemets ad data segmets.) There is o oe-to-oe correspodece betwee X12 ad EDIFACT data elemets; multiple X12 data elemets may be eeded to represet a sigle EDIFACT data elemet. Architecture Overview The X12 ad EDIFACT stadards are hierarchical sets of message elemet structures. At the bottom of each hierarchy, simple data structures are combied to form more complex data structures. The top of each message structure hierarchy is populated by iformatio uits exchaged by tradig parters. Differet hierarchies ad data structures are defied for differet data sets. For example, a X message (a Fuctioal Ackowledgmet) is quite differet from a X message (a Ivoice), ad the requiremets for both are differet from those for a X message (a Studet Educatioal Record, or trascript). Message Structure At the base of each EDI stadard is a dictioary of simple data elemets. A simple data elemet represets the smallest amed item i a X12 or EDIFACT stadard, such as a qualifier, a value, or a descriptio. Examples of simple data elemets iclude: 1-2 Usig EDI with WebLogic Itegratio

15 What Is EDI? Ivoice date Weight capacity Exchage rate Hazardous material classificatio Uit of measuremet code (such as pouds, dozes, cubic feet, gallos, ad so o) The X12 stadard also defies a composite data elemet. A composite data elemet is a set of simple data elemets that represets a sigle amed item. For example, i a X message, the composite data elemet C002 is used to idetify the actios to be performed o a piece of paperwork, ad comprises five simple data elemets. Each simple data elemet is a code idetifyig oe required actio. Data elemets are grouped ito fuctioally related uits called data segmets. A example of a data segmet is the address of a geographic locatio, which icludes the data elemets for a city ame, a state or provice code, a postal code, ad a coutry code. Data segmets are defied i the X12 segmet directory, which lists the data elemets, i the required order, that make up each data segmet. Data segmets are grouped, i tur, ito trasactio sets. A trasactio set is the smallest meaigful set of iformatio exchaged by tradig parters. It represets a commo busiess documet, such as a purchase order or ivoice. Most trasactio sets are divided ito three areas (called tables), each of which correspods to a part of a prited documet: Table 1, the Trasactio Set Header, is the headig area, i which iformatio pertiet to the etire trasactio is placed. Table 2, the detail area, is composed of oe or more data segmets. For example, the lie items for a purchase order are placed i the detail area. Table 3, the Trasactio Set Trailer, is the summary area, which cotais iformatio such as the umber of data segmets used i a trasactio set. Usig EDI with WebLogic Itegratio 1-3

16 1 EDI Backgroud Figure 1-1 Structure of a Trasactio Set Although a trasactio set represets a prited documet, it is ot the iformatio uit exchaged i a EDI trasactio. Similar trasactio sets are arraged ito fuctioal groups. For example, if Compay A seds Compay B two Requests for Quotatios (RFQs) ad five Purchase Orders (POs), the two RFQs are combied ito oe fuctioal group, ad the five POs are combied ito aother. All fuctioal groups destied for a particular tradig parter are the combied ito a iformatio uit called a EDI iterchage. It is these iterchages that are trasmitted betwee tradig parters. With the advet of readily-available high-speed etworkig, may EDI systems have moved to real-time EDI iterchage, i which each trasactio set is trasmitted to a tradig parter, if possible, as it arrives at the EDI system as a separate EDI iterchage. I older systems, trasactio sets are batched together ad trasmitted as oe or more composite EDI iterchages. Because of the breadth ad depth of EDI peetratio ito the e-commerce marketplace, you may ecouter both situatios with your tradig parters. The fuctioal groups of a iterchage are wrapped withi a iterchage header ad trailer. The header provides cotrol iformatio: Seder ad receiver of the iterchage Date ad time of the iterchage 1-4 Usig EDI with WebLogic Itegratio

17 What Is EDI? Stadard ad versio of the iterchage Authorizatio ad security iformatio Uique cotrol umber by which the iterchage ca be tracked. The trailer eds the iterchage. It provides the total umber of fuctioal groups i the iterchage, ad it repeats the uique iterchage cotrol umber idetified i the header. The followig illustratio shows how all of this is put together to form a X12 EDI message. EDIFACT ad TRADACOMS messages use similar, though ot idetical, message structures. Figure 1-2 X12 Message Structure Differeces with Other E-Commerce Stadards E-commerce stadards other tha EDI, such as RosettaNet, BizTalk, ad CXML are desiged to take advatage of state-of-the-are techology, but they are ot completely free of restrictios. Geerally, these e-commerce stadards require the followig: Use of HTTP ad/or HTTPS as the stadard trasport protocol Use of XML to package data Assume real-time access to tradig parters Usig EDI with WebLogic Itegratio 1-5

18 1 EDI Backgroud Structure that supports delivery of oe trasactio per datagram I additio, because these stadards are relatively ew, they are geerally restricted to a small idustry segmet, with a relatively limited umber of trasactio messages available. At the same time, other e-commerce stadards evolve relatively quickly, addig ew fuctioality very quickly. I cotrast, EDI offers a wide variety of already-established stadards, icludig the three most commo - X12, EDIFACT, ad TRADACOMS. These stadards provide a wide variety of trasactio types, addressig a broad variety of idustry ad govermet segmets. EDI Stadards Curretly, there are three primary EDI stadards: X12, EDIFACT, ad TRADACOMS. X12 The X12 stadard is maitaied by the ANSI Accredited Stadards Committee ( It is used primarily withi the U.S. ad North America. The U.S. Federal govermet has chartered the Natioal Istitute of Stadards ad Techology to maitai a Federal registry of all EDI implemetatio stadards as they are used by the Federal govermet. For details, go to ( New releases of the X12 stadard, icorporatig techical updates ad ew EDI trasactios, are published regularly. 1-6 Usig EDI with WebLogic Itegratio

19 BEA WebLogic EDI Itegratio Architecture EDIFACT The EDIFACT stadard is maitaied by the Uited Natios/Ecoomic Commissio for Europe (UN/ECE) ad the Iteratioal Stadards Orgaizatio ( The EDIFACT stadard is used primarily withi Europe. TRADACOMS The TRADACOMS stadard was developed ad is maitaied by the ANA (Article Numberig Associatio) ( It is used primarily i the U.K. retail idustry. BEA WebLogic EDI Itegratio Architecture BEA provides comprehesive EDI support through the BEA WebLogic Adapter for Power.Eterprise! 3.0 ad Power.Eterprise! software. Figure 1-3 illustrates how the BEA WebLogic Adapter for Power.Eterprise! ad Power.Eterprise! software work together put WebLogic Itegratio to work with your tradig parters EDI systems. Figure 1-3 BEA EDI Itegratio Architecture Usig EDI with WebLogic Itegratio 1-7

20 1 EDI Backgroud BEA WebLogic Adapter for Power.Eterprise! The BEA WebLogic Adapter for Power.Eterprise! provides a gateway betwee WebLogic Itegratio ad the Power.Eterprise! software. Usig stadard applicatio itegratio evets ad services that you defie usig BEA WebLogic techology, BEA WebLogic Adapter for Power.Eterprise! allows you to: Exchage XML documets with your tradig parter, via Power.Eterprise! Receive documets from a tradig parter via Power.Eterprise! Power.Eterprise! Software Power.Eterprise! is a suite of three compoets: Power.Server!, Power.Map!, ad Power.Maager!. These compoets eable you to defie your EDI to XML documet maps, maage your tradig parter relatioships, ad hadle the trasmissio ad receipt of EDI messages. 1-8 Usig EDI with WebLogic Itegratio

21 CHAPTER 2 Architecture The followig sectios describe the architecture of EDI Itegratio, icludig iformatio about the BEA WebLogic Adapter for Power.Eterprise!, the Power.Eterprise! software, ad VAN/etwork coectivity: EDI Itegratio Architecture Power.Eterprise! Architecture VAN ad Network Coectivity EDI Itegratio Architecture BEA provides comprehesive EDI support usig the BEA WebLogic Adapter for Power.Eterprise! ad the Power.Eterprise! software suite. Figure 2-1 shows how the BEA WebLogic Adapter for Power.Eterprise! ad Power.Eterprise! combie to put WebLogic Itegratio to work with your tradig parters EDI systems. Figure 2-1 BEA EDI Itegratio Architecture The EDI Adapter uses applicatio itegratio to allow WebLogic Itegratio to exchage XML documets with Power.Eterprise!, usig RMI message passig. Usig EDI with WebLogic Itegratio 2-1

22 2 Architecture The Power.Server! compoet of Power.Eterprise! provides EDI Itegratio with capabilities for trasformig, trasmittig, ad receivig EDI messages. Power.Eterprise! provides ru-time, maagemet, ad mappig tools to resolve all EDI trasactios with idividual tradig parters i real time. Power.Eterprise! Architecture The Power.Eterprise! software provides a uified, Java-based workig eviromet i which you ca map your outgoig documet trasmissios to appropriate EDI documets ad maage your relatioships with tradig parters. This eviromet comprises three compoets: Power.Server!: This Java-based ru-time server provides dispatch ad receive services for your EDI message traffic. It executes trasactios with tradig parters defied usig Power.Maager!. Icomig ad outgoig messages are trasformed i accordace with the defiitios you establish usig Power.Map!. Power.Maager!: This applicatio allows you to maage multiple Power.Server! istaces across multiple machies by defiig tradig parter relatioships ad coectio iformatio for all your tradig parters. Power.Map!: This applicatio eables you to load, create, ad store maps betwee the various data formats you use ad commo EDI data structures. By usig Power.Map! you ca create simple mappig rules for elemetary coversios, or use formulas or JavaScript for more complex ad sophisticated coversios. Feature Overview Power.Eterprise! provides a complete solutio for the trasformatio ad delivery of messages: Power.Server! provides a real-time data-trasformatio egie, with support for ANSI X12, UN/EDIFACT, ad TRADACOMS data formats. 2-2 Usig EDI with WebLogic Itegratio

23 Power.Eterprise! Architecture Power.Map! is a extesible mappig tool that provides drag-ad-drop fuctioality for your mappig. It also allows you to use formulas or JavaScript code for more complex coversios. Power.Maager! is the cofiguratio ad maagemet tool, which allows you to cofigure tradig parter relatioships ad sigle-directio coectios. Power.Eterprise! is also equipped with IP-level coectivity to the Get2Coect VAN, ad it supports a variety of stadard etwork coectio protocols. Supported Stadards Power.Eterprise! supports the followig EDI ad data stadards: X12 EDIFACT TRADACOMS XML Flat file Limitatios Curretly the Power!Eterprise suite is available o the followig systems: Power.Server! is available for Widows NT/2000, Solaris, HPUX, ad AIX systems. Power.Eterprise! requires a SQL database to fuctio. It supports Oracle 8i (8.1.7 or later), Microsoft SQLServer 7.0 or 2000, ad IBM DB2 databases. Power.Map! ad Power.Maager! are available oly for Widows NT/2000 systems. Usig EDI with WebLogic Itegratio 2-3

24 2 Architecture Power.Map! Power.Map! is a tool that defies the data format-mappig capabilities available i Power.Eterprise!. It supports coversio of data ito ad out of EDI formats, allowig you to choose ay documet structure stadard supported by Power.Map!, while maitaiig your ability to iteroperate with a variety of stadard ad tradig parter-specific EDI formats. Power.Map! requires three items: Data defiitio for the source documet Data defiitio for the target documet Map of liks betwee data i the source documet ad data i the target documet You must provide separate data defiitios, such as DTDs or XSDs, for ay data format ot already defied i Power.Map!. With Power.Map! you ca build XML data structures withi the applicatio, or you ca import DTDs ad schemas that are exterally created. Oce those documets are imported ito Power.Map!, you ca defie a map for them. Although Power.Map! supports the import of XML DTDs ad schemas for data defiitios, it does ot provide a data format export capability; documet formats may oly be imported. For this reaso, you should desig your data iterchage documets outside Power.Map!, the import a copy to Power.Map! to create a map. Power.Map! icludes built-i defiitios for most stadard EDI messages, icludig support for X12, EDIFACT, ad TRADACOMS messages. Creatig ad Maitaiig Maps Power.Map! allows you to create, maitai, ad test maps off-lie, that is, without ay coectios to a server. These maps are based o documet defiitios that you may import, EDI documet defiitios supplied with Power.Map!, ad custom defiitios that you may defie. Power.Map! allows you to export a map that you have defied, or import a map created elsewhere. 2-4 Usig EDI with WebLogic Itegratio

25 Power.Eterprise! Architecture Creatig ad Maitaiig Documets Documet defiitios that you ited to use with Power.Server! should be maitaied separately. Power.Map! supports oly the import of XML DTDs ad XSDs. These documets caot be used outside Power.Map! (for example, they caot be used i WebLogic Itegratio) uless they are created outside Power.Map!. I additio, you should verify the EDI documet stadards that you will be usig. While a variety of stadards ad versios are supported withi Power.Eterprise!, the specific trasactio, stadard, ad versio that you are usig may ot be supported. If you are usig a usupported trasactio, stadard, or versio, cotact BEA Customer Support. Power.Maager! Power.Maager! is used to maitai ad maage your servers ad tradig parter relatioships. Power.Maager! allows you to maage multiple istaces of Power.Server! from a sigle, remote locatio. Tradig Parter Maiteace Coectios Power.Maager! provides facilities for maitaiig tradig parter defiitios ad the data associated with them. These tradig parter defiitios are specific to EDI Itegratio; they are ot shared with or available to ay other compoets of the BEAWebLogic Itegratio system. Power.Maager! allows you to maitai multiple simultaeous coectios. Each coectio defies a flow of iformatio i oe directio, either to or from the Power.Server! Thus, a sigle coectio might defie the RMI trasfer of documets from Power.Server! to the EDI Adapter. A secod coectio might defie the receptio, by Power.Server!, of EDI documets set by a tradig parter via the Get2Coect VAN. Usig EDI with WebLogic Itegratio 2-5

26 2 Architecture Exchage Profiles Power.Maager! allows you to defie multiple exchage profiles to maage the flow of documets with your tradig parters. Each exchage profile maages a sigle set of documets that: Flows i oe directio, from a source to a destiatio Cotais two coectios Cotais a map Documet Trackig Admiistratio A exchage profile, for example, may cotai a coectio that govers the receptio of a EDI documet from a tradig parter via the Get2Coect VAN, a map that trasforms that EDI documet ito a XML documet, ad a secod coectio defiitio that seds the resultig XML documet to the EDI Adapter via RMI. Power.Maager! provides tools for loggig, reportig, ad trackig so you ca moitor your documets i real time. Power.Maager! allows you to maage multiple servers. You ca maage documets, view ad cofigure loggig, ad establish error-hadlig procedures o the server from a sigle remote applicatio. VAN ad Network Coectivity EDI trasactios are ofte executed through oe or more proprietary etworks, called Value-Added Networks (VANs). VANs are created ad customized for a specific vertical or horizotal idustry segmet, such as the followig: Geeral Electric Global Exchage Services (GE GXS) is oe of the largest VANs i the world. GXS provides wide-ragig VAN services throughout the world, with over 100,000 tradig parters exchagig $1 trillio i goods ad services each year. 2-6 Usig EDI with WebLogic Itegratio

27 VAN ad Network Coectivity Telefoica Servicios Avazados de Iformacio (TSAI) is a example of a horizotal-idustry segmet VAN. It is the primary Spaish-laguage VAN, servig a variety of idustries. Approximately $1.25 billio i busiess is hadled by the TSAI VAN each year, which accouts for 60 percet of Spai s EDI busiess. PaperVa, a example of a vertical-idustry segmet VAN, is a VAN for the paper products idustry. I additio to etworkig services, it provides cosultig ad implemetatio support. WalMart has established a proprietary VAN as part of its EDI strategy, aimed at maagig the acquisitio ad distributio of products. To implemet this strategy, WalMart provides its suppliers with a comprehesive stadard for coectig with their implemetatio of EDI ad their VAN. May compaies implemetig EDI are also experimetig with direct trasactio hadlig, either over proprietary etworks or via the Iteret. The field trials of these implemetatios idicate that security over the Iteret is ot a issue. Power.Eterprise! supports all the commuicatio optios described here. You may perform trasactios with a parter usig ay of the followig coectio methods: Over a proprietary VAN, usig the Cleo A+ software Via a direct etwork coectio Via the Iteret (HTTP, HTTPS, ad FTP coectios are all supported) Usig the Get2Coect VAN (with built-i support) Power.Eterprise! provides coectivity to a geeric VAN called Get2Coect.et which is ot targeted to a specific idustry. To coect to other VANs, Power.Eterprise! also icludes the use of a trial licese for Cleo A+, which is a commuicatio package for Widows systems that allows you to exchage files with other micro, mii, ad maiframe computers that support asychroous commuicatios. Usig EDI with WebLogic Itegratio 2-7

28 2 Architecture 2-8 Usig EDI with WebLogic Itegratio

29 CHAPTER 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 The BEA WebLogic Adapter for Power.Eterprise! 3.0 is a implemetatio of the applicatio itegratio capability i BEA WebLogic Itegratio. The BEA WebLogic Adapter for Power.Eterprise! eables you to sed ad receive XML messages that are trasformed ito ad from EDI messages by Power.Eterprise!. This sectio icludes the followig topics: Overview of Applicatio Itegratio Usig the Adapter Plug-I to the BEA WebLogic Itegratio Studio Exceptio Hadlig Overview of Applicatio Itegratio BEA WebLogic Itegratio is described i Itroducig Applicatio Itegratio. For more iformatio about implemetig ad usig applicatio itegratio fuctioality, see Usig Applicatio Itegratio. BEA WebLogic Itegratio s itegratio solutio supports existig ad future stadards for coectig applicatios both withi ad betwee eterprises. BEAWebLogic Itegratio provides a meas to defie commuicatio edpoits, Usig EDI with WebLogic Itegratio 3-1

30 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 which you may add to a process flow through the busiess process maagemet (BPM) fuctioality of BEA WebLogic Itegratio or by usig custom code to form a complete itegratio solutio. As discussed previously, the BEA WebLogic Adapter for Power.Eterprise! is implemeted usig the itegratio fuctioality provided by BEA WebLogic Itegratio. The remaider of this chapter discusses this fuctioality as it applies to the BEA WebLogic Adapter for Power.Eterprise!. Applicatio Views To accomplish message-level eterprise applicatio itegratio, you ca create ay umber of applicatio views for each adapter. A applicatio view defies a set of busiess fuctios o a specific adapter. The applicatio view, via the uderlyig adapter, supports evets ad services for a particular busiess use. Evets eable messages geerated by a applicatio to be maaged i accordace with a publish ad subscribe model. Services are busiess fuctios that may be ivoked by a user. Service ivocatios cause messages to be set to a applicatio i accordace with a request/respose model. Requests ad resposes for both evets ad services are passed through the system as XML documets. For more iformatio about applicatio views, see Uderstadig the Itegratio Framework i Itroducig Applicatio Itegratio. The BEA WebLogic Adapter for Power.Eterprise! view provides multiple applicatio views, each cotaiig multiple user-defiable services ad evets. Both services ad evets are defied by XML schemas, ad both trasmit data i XML form. This method allows ay XML-aware compoet, such as WebLogic Itegratio, to use the BEA WebLogic Adapter for Power.Eterprise! for commuicatio with Power.Eterprise!. BEA WebLogic Adapter for Power.Eterprise! applicatio views, services, ad evets are maaged from the WebLogic Applicatio Itegratio Adapter home page. Before the BEA WebLogic Adapter for Power.Eterprise! ca operate properly with Power.Eterprise!, you must cofigure it to do so. You must also cofigure the Adapter services ad evets. 3-2 Usig EDI with WebLogic Itegratio

31 Overview of Applicatio Itegratio To facilitate these cofiguratio tasks, BEA WebLogic Adapter for Power.Eterprise! applicatio view provides three Java Server Pages (JSPs). Cofigurig the BEA WebLogic Adapter for Power.Eterprise! To eable the BEA WebLogic Adapter for Power.Eterprise! to commuicate with Power.Eterprise!, you must cofigure it with suitable commuicatio iformatio. To cofigure the BEA WebLogic Adapter for Power.Eterprise!: 1. From the BEA WebLogic Itegratio Applicatio View Cosole, select Defie New AppView. Figure 3-1 Defie New Applicatio View JSP Usig EDI with WebLogic Itegratio 3-3

32 3 BEA WebLogic Adapter for Power.Eterprise! Select Cofigure Coectio. The Cofigure Coectio JSP is displayed. Figure 3-2 Cofigure Coectio JSP 3. Eter the hostame or IP address of the system o which the Power.Server! resides. 4. Eter the port umber used by Power.Eterprise! for RMI commuicatios. The default is Select Coect to EIS. 6. Click Add Service, ad defie ay services you wat exposed usig the procedure i Cofigurig Services. 7. Click Add Evet, ad defie ay evets you wat exposed usig the procedure i Cofigurig Evets. 3-4 Usig EDI with WebLogic Itegratio

33 Overview of Applicatio Itegratio Figure 3-3 Cofiguratio Admiistratio JSP 8. Set the coectio criteria based o your requiremets. May of these criteria are automatically geerated based o the iformatio you have already etered ad your system cofiguratio. Whe you are fiished, select Cotiue. The Deploy Applicatio View widow appears. Usig EDI with WebLogic Itegratio 3-5

34 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 Figure 3-4 Deploy Applicatio View JSP 9. Set ay parameters ecessary, ad select Deploy. Your cofigured applicatio view is deployed. Note: Always start the Power.Server! before you start WebLogic Itegratio or WebLogic Server. The WebLogic Itegratio coectors expect to see a active istace of the Power.Server! whe they are iitialized, ad they will throw exceptios if Power.Server! is ot ruig whe they are iitialized. Evets A evet cotais a XML documet that is published by a applicatio view whe a evet of iterest occurs. Cliets that wat to be otified of evets register their iterest with a applicatio view. After a cliet subscribes to evets published by a applicatio view, the applicatio view otifies the cliet wheever a subscribed evet occurs withi the target applicatio, ad the passes the cliet a XML documet that 3-6 Usig EDI with WebLogic Itegratio

35 Overview of Applicatio Itegratio Cofigurig Evets describes the evet. For more iformatio about evets, see Addig ad Evet to a Applicatio View i Defiig a Applicatio View i Usig Applicatio Itegratio. The BEA WebLogic Adapter for Power.Eterprise! provides user-defiable evets. These evets are created ad maaged usig a Java Server Page, which is published as part of the WebLogic Itegratio Applicatio Iterface. Whe Power.Eterprise! receives a EDI message from a tradig parter ad forwards it to the BEA WebLogic Adapter for Power.Eterprise!, the Adapter publishes the appropriate evets. The process works as follows: 1. Upo receipt of a EDI documet from a tradig parter, Power.Eterprise! traslates the documet to XML. 2. Usig RMI, Power.Eterprise! ivokes BEA WebLogic Adapter for Power.Eterprise! with a previously registered evet. 3. WebLogic Itegratio publishes the defied evet. Evets are used by the BEA WebLogic Adapter for Power.Eterprise! to sed iformatio from a workflow to Power.Eterprise!, which forwards it to your tradig parter. The BEA WebLogic Adapter for Power.Eterprise! allows you to defie multiple evets. As a rule, you will defie oe evet per XML/EDI documet type (a purchase order, for example) that you pla to sed. To defie a evet o the BEA WebLogic Adapter for Power.Eterprise!: 1. O the BEA WebLogic Adapter for Power.Eterprise! home page, click Add Evet. Usig EDI with WebLogic Itegratio 3-7

36 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 Figure 3-5 Cofigure Evet JSP 2. Eter a ame for the evet that is uique withi the BEA WebLogic Adapter for Power.Eterprise!. 3. If you like. Eter a descriptio. (This step is optioal.) 4. Eter the hostame or IP address of the system o which the Power.Server! process resides. 5. Eter the umber of the port used by the RMI listeer process. 6. Eter the RMI service ame of the listeer process as defied for Power.Eterprise!. 3-8 Usig EDI with WebLogic Itegratio

37 Overview of Applicatio Itegratio Testig a Evet After you cofigure both evets ad your workflows, you should test that you ca successfully sed messages through those evets. Use the Test Evet lik to test your evet withi the Applicatio View cosole. The followig procedure is a simple test method to test how a evet receives a message: 1. Cofigure Power.Eterprise! such that it temporarily uses a file coectio to sed to your tradig parter. 2. Sed a message through the system, ad dump the resultig EDI message to a file. 3. Examie the file cotaiig the message to make sure that the message was created ad set correctly. 4. Whe you fiish testig, recofigure the coectio to use the trasport appropriate to your tradig parter. Services A service is a busiess operatio i a applicatio that is exposed by the applicatio view. It fuctios as a request/respose mechaism: whe a applicatio receives a request to ivoke a busiess service, the applicatio view ivokes that fuctioality i its target applicatio ad the respods with a XML documet that describes the results. For more iformatio about services, see Addig a Service to a Applicatio View i Defiig a Applicatio View i Usig Applicatio Itegratio. The BEA WebLogic Adapter for Power.Eterprise! provides user-cofigurable services. These services are created ad maaged usig a Java Server Page, which is published as part of the WebLogic Itegratio Applicatio Iterface. They are used to sed XML to Power.Eterprise!, which, i tur, coverts the XML message to a EDI message ad seds the EDI message to a tradig parter. To sed a EDI message, submit a appropriately formatted XML documet to the service defied for BEA WL Adapter for Power.Eterprise!. The service uses RMI to pass the message to Power.Eterprise!, which traslates the XML message to a EDI message format ad dispatches it to the appropriate tradig parter. Usig EDI with WebLogic Itegratio 3-9

38 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 Cofigurig Services Services are used by the BEA WebLogic Adapter for Power.Eterprise! to receive iformatio for a workflow that is forwarded from your tradig parter by Power.Eterprise!. Although the BEA WebLogic Adapter for Power.Eterprise! allows you to defie multiple services, most situatios require you to defie oly oe evet per XML/EDI documet type (such as a EDI 855 message) that you pla to receive. To defie a service o the BEA WebLogic Adapter for Power.Eterprise!: 1. O the BEA WebLogic Adapter for Power.Eterprise! home page, click Add Service. The Cofigure Service JSP is displayed. Figure 3-6 Cofigure Service JSP 2. Eter a ame for the service that is uique withi the BEA WebLogic Adapter for Power.Eterprise! Usig EDI with WebLogic Itegratio

39 Usig the Adapter Plug-I to the BEA WebLogic Itegratio Studio Testig a Service 3. Eter a descriptio. (This step is optioal.) 4. Eter the ame of the RMI source coectio, defied uder Power.Eterprise!, from which this service ca expect to receive messages. After you cofigure both services ad the workflows that will use those services, you should verify that you ca properly receive messages from them. Use the Test Service lik to test your evet withi the Applicatio View cosole. The followig procedure is a simple test method to test how a service delivers a message: 1. Cofigure Power.Eterprise! such that it temporarily uses a iboud file coectio. 2. Drop a file ito a outbox to start a test sequece. The resultig message should be trasformed by Power.Eterprise, the set to your workflow. 3. I your workflow, examie the message to make sure that it was created ad received correctly. 4. Whe you fiish testig, recofigure the coectio to use the trasport appropriate to your tradig parter. Usig the Adapter Plug-I to the BEA WebLogic Itegratio Studio The BEA WebLogic Adapter for Power.Eterprise! icludes a plug-i to the BEA WebLogic Itegratio Studio, a graphical tool for modelig for busiess processes. Because the Adapter is a itegral part of BEA WebLogic Itegratio, you ca use this plug-i for EDI message hadlig ad itegratio i exactly the same way you use ay other applicatio itegratio adapter. Usig EDI with WebLogic Itegratio 3-11

40 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 For more iformatio about BPM workflow desig usig adapters ad the adapter plug-i to the BEA WebLogic Itegratio Studio, see Uderstadig the Applicatio Itegratio Plug-i for BPM ad Uderstadig the ADK i Itroducig Applicatio Itegratio. Deployig a Adapter i a New WebLogic Itegratio Domai For Widows Systems: If you wat to deploy a istace of the BEA WebLogic Adapter for Power.Eterprise! 3.0 i a ew domai, follow these steps: Before you begi, you must determie the locatio of the adapter ear ad jar file o your computer. By default, they are located i WLI_HOME\adapters\powereterprise\lib. 1. Declare the adapter's EAR file i your domai's cofig.xml file. Listig 3-1 Widows Cofig.XML Domai Declaratio <Applicatio Deployed="true" Name="BEA_POWERENTERPRISE_3_0" Path="WLI_HOME\adapters\powereterprise\lib\BEA_POWERENTERPRISE_3_0_EAR.ear"> <CoectorCompoet Name="BEA_POWERENTERPRISE_3_0" Targets="myserver" URI="BEA_POWERENTERPRISE_3_0.rar"/> <WebAppCompoet Name="BEA_POWERENTERPRISE_3_0_EvetRouter" Targets="myserver" URI="BEA_POWERENTERPRISE_3_0_EvetRouter.war"/> <WebAppCompoet Name="BEA_POWERENTERPRISE_3_0_Web" Targets="myserver" URI="BEA_POWERENTERPRISE_3_0_Web.war"/> </Applicatio> 2. Add the followig JAR files i the WebLogic server classpath. WLI_HOME\lib\hlcommo.jar WLI_HOME\lib\mekshared.jar WLI_HOME\lib\powerapi.jar 3-12 Usig EDI with WebLogic Itegratio

41 Exceptio Hadlig WLI_HOME\adapters\powereterprise\lib\ BEA_POWERENTERPRISE_3_0.jar For UNIX Systems Before you begi, you must determie the locatio of the adapter ear ad jar file o your computer. By default, they are located i WLI_HOME/adapters/powereterprise/lib. 1. Declare the adapter's EAR file i your domai's cofig.xml file: Listig 3-2 UNIX Cofig.XML Domai Declaratio <Applicatio Deployed="true" Name="BEA_POWERENTERPRISE_3_0" Path="WLI_HOME/adapters/powereterprise/lib/BEA_POWERENTERPRISE_3_0_EAR.ear"> <WebAppCompoet Name="BEA_POWERENTERPRISE_3_0_EvetRouter" Targets="myserver" URI="BEA_POWERENTERPRISE_3_0_EvetRouter.war"/> <CoectorCompoet Name="BEA_POWERENTERPRISE_3_0" Targets="myserver" URI="BEA_POWERENTERPRISE_3_0.rar"/> <WebAppCompoet Name="BEA_POWERENTERPRISE_3_0_Web"Targets="myserver" URI="BEA_POWERENTERPRISE_3_0_Web.war"/> </Applicatio> 2. Add the followig JAR files i the WebLogic Server classpath. WLI_HOME/lib/hlcommo.jar WLI_HOME/lib/mekshared.jar WLI_HOME/lib/powerapi.jar WLI_HOME/adapters/powereterprise/lib/BEA_POWERENTERPRISE_3_0.j ar Exceptio Hadlig The respose schema for a service method should iclude both a status Code ad a Message: Usig EDI with WebLogic Itegratio 3-13

42 3 BEA WebLogic Adapter for Power.Eterprise! 3.0 Code returs Success or Failure. Message correspods to a message retured by Power.Eterprise! whe a service call is iitiated. To hadle ay exceptio that may occur, create a XPath expressio to retrieve the status code from ay respose XML. The followig is a example of the respose schema for a service call: <Status> <Code>Success </Code> <Message>Traslatio Request Queued Successfully.</Message> </Status> The Code ca be extracted from the respose schema usig the followig Xpath expressio: "/Status/Code/text()" Usig EDI with WebLogic Itegratio

43 CHAPTER 4 Cofigurig Power.Eterprise! This sectio describes the istallatio ad cofiguratio of Power.Eterprise! ad its associated software: Istallig Power.Eterprise! Cofigurig Power.Eterprise! Cofigurig Tradig Parters Mappig XML ad EDI Data Coectios ad VAN Coectivity Cofigurig Exchage Profiles Istallig Power.Eterprise! Power.Eterprise! is delivered i two packages that must be istalled separately. I additio, you may wat to istall Cleo A+ to maage VAN coectivity issues. If you pla to istall both Power.Server! ad Power.Cliet! o the same machie, you must istall them i separate directories. Power.Server! is the ru-time server. Before you ca istall this package, your eviromet must meet the followig prerequisites: Usig EDI with WebLogic Itegratio 4-1

44 4 Cofigurig Power.Eterprise! l l l l l Operatig System: Microsoft Widows NT 4.0 SP6, Widows 2000 SP1, Su Solaris 7, HP UX 11, or IBM AIX Java: Su JRE/JDK 1.3 or later Memory: 512MB miimum, 1GB recommeded Disk space: 100MB SQL Database: Power.Server! requires access to a SQL database. Power.Server! supports Oracle 8i, Microsoft SQL Server 2000, ad IBM DB2 versio 7.1.You must provide the hostame, coectio port, database ame, ad logi iformatio for the database durig istallatio. BEA WebLogic Itegratio icludes a 30-day trial licese commo to all Power.Eterprise! software. To receive a sigle, full-use licese for Power.Server!, cotact your BEA sales represetative. Oe Power.Eterprise! licese is available for each BEA WebLogic Itegratio licese. Power.Cliet! cotais Power.Map! ad Power.Maager!. Before you ca istall this package, your eviromet must meet the followig prerequisites: l Operatig System: Microsoft Widows NT 4.0 SP4 or Widows 2000 l l l Java: Su JRE/JDK 1.3 or later Memory: 256MB Disk space: 50MB l Iteret Explorer 5.0 BEA WebLogic Itegratio icludes a 30-day trial licese commo to all Power.Eterprise! software. Power.Cliet! uses this licese key Cleo A+ is a asychroous commuicatios maagemet package used to cotrol VAN commuicatios with your tradig parter. If you are usig a VAN other tha Get2Coect, ad you eed asychroous commuicatios maagemet, istall the Cleo A+ software. For more iformatio about istallig Cleo A+, go to the followig URL: For iformatio about obtaiig a productio licese for Cleo A+, cotact Cleo Commuicatios. 4-2 Usig EDI with WebLogic Itegratio

45 Istallig Power.Eterprise! Gettig Liceses Whether you dowload Power.Eterprise! as part of the WebLogic Itegratio 2.1 istallatio or istall it from CD media, you will eed to obtai your Power.Eterprise! 3.0 evaluatio licese from the BEA website at the followig URL: A Power.Eterprise! productio licese is provided whe you purchase BEA WebLogic Itegratio. For more iformatio, please cotact your BEA sales represetative. I additio, you may dowload ad istall a 30-day trial of Cleo A+, for hadlig VAN coectivity. To covert your trial licese to a productio licese, cotact Cleo Commuicatios. Access to the Get2Coect.Net VAN is icluded with the BEA WebLogic Adapter for Power.Eterprise!. To use Get2Coect.Net, cotact Peregrie Customer Support through their Web site at Istallig the Power.Server! To istall the Power.Server! software, you must fulfill the prerequisites listed i the previous sectios of this documet. For geeral iformatio about istallig Power.Server!, see Istallig the Power.Eterprise! Software i Istallig BEA WebLogic Itegratio. Istallig the Power.Cliet! To istall the Power.Cliet! software (specifically Power.Map! ad Power.Maager!), you must fulfill the prerequisites listed uder Istallig Power.Eterprise! o page 4-1. For geeral iformatio about istallig Power.Map! ad Power.Maager!, see Istallig the Power.Eterprise! Software i Istallig BEA WebLogic Itegratio. Usig EDI with WebLogic Itegratio 4-3

46 4 Cofigurig Power.Eterprise! Coectig to Get2Coect.Net To use Get2Coect.Net, you must have the Power.Eterprise! software istalled. You must also have a valid Product Serial Number (PSN) to register as a Get2Coect.Net tradig parter. To get a valid PSN, cotact BEA Customer Support. Istallig Cleo A+ If you ited to use Cleo A+ for VAN commuicatios, go to the followig URL: This Web page provides dowloadable istallatio sets for all platforms supported by Power.Server!, as well as istallatio ad user documetatio. The dowloadable software icludes a trial licese. For productio licesig, cotact Cleo Commuicatios. Dowloadig Software Updates Power.Eterprise! is desiged to be updated with dowloaded software patches from the BEA Customer Service Web site. To istall software patches for Power.Eterprise!: 1. From withi Power.Maager! click Self Service, the click Software Update. 2. Click Step 1: Select Software. This lauches a Web browser which automatically coects to the BEA Customer Service web page, listig all software update files available for dowload. Istructios for istallatio of these updates are also icluded o this Web page. Updatig EDI Documet Descriptios Power.Eterprise! ships with defiitios for may stadard EDI documets icluded. BEA will also make ew defiitio sets available through BEA Customer Service. 4-4 Usig EDI with WebLogic Itegratio

47 Istallig Power.Eterprise! To istall ew stadards dowloaded from the BEA Customer Service Web site: 1. From withi Power.Maager! click Self Service, the click Stadards Update. 2. Click Step 1: Select Stadards. This lauches a Web browser which automatically coects to the BEA Customer Service web page, listig all EDI defiitio files available for dowload. 3. Select ad dowload the EDI defiitio files that you require. 4. Place the dowloaded files ito the followig directory: Power_Server_istall_dir\dowloads\metadata\ 5. Stop, the restart the Power.Server o which you have istalled the defiitio file. 6. Remove the dowloaded files from the followig directory: Power_Server_istall_dir\dowloads\metadata\ 7. To access the documet descriptios from withi Power.Map!, check them out from the server. Coectig to a Server for the First Time Before you ca log i to Power.Maager! or Power.Map!, you must create a Power.Server! coectio. Subsequetly, you ca use the same procedure to coect to other istaces of Power.Server!, allowig you to maage multiple istaces of Power.Server! from a sigle cosole. All coectio data is persistet: oce you create a coectio, it will be available every time you start Power.Maager!. To create a coectio: 1. Log i to Power.Maager! or Power.Map by choosig Start Meu Programs Power.It. Select the appropriate applicatio. To create a server coectio, Power.Server! must be ruig o the machie to which you wat to coect. Usig EDI with WebLogic Itegratio 4-5

48 4 Cofigurig Power.Eterprise! Figure 4-1 Power.Maager! Server Coectio Dialog Box 2. Click Add to add a ew Power.Server! coectio. Figure 4-2 Power.Maager! Server Add Dialog Box 3. Eter the Server Hostame ad Server Cotrol Port of the Power.Server!. Click Add. A list of defied istaces of Power.Server! is displayed. 4. Select the Power.Server! to which you wat to coect from the list of defied coectios. Click Coect. The Power.Maager! Server Coectio dialog box is displayed. 4-6 Usig EDI with WebLogic Itegratio

49 Cofigurig Power.Eterprise! Figure 4-3 Power.Maager! Server Coectio Dialog Box Cofigurig Power.Eterprise! Power.Eterprise! allows you to cofigure multiple coectios to the BEA WebLogic Adapter for Power.Eterprise!. Each coectio to the BEA WebLogic Adapter for Power.Eterprise! is defied as a separate RMI coectio, either sedig data to or receivig data from Power.Eterprise!. All other cofiguratio required by Power.Eterprise! is desiged to cofigure tradig parters, maps, exteral coectios, ad exchage profiles. Whe iitially cofigurig Power.Eterprise!, be sure to cofigure the followig etities i the order show: Tradig parters Maps Coectios Exchage profiles Usig EDI with WebLogic Itegratio 4-7

50 4 Cofigurig Power.Eterprise! Cofigurig Tradig Parters To use EDI Itegratio with WebLogic Itegratio, you must eter your tradig parter data ito both Power.Eterprise! ad WebLogic Itegratio. No mechaism exists to move tradig parter data either to or from Power.Eterprise!, so you ay tradig parter data registered with WebLogic Itegratio must also be etered ito Power.Eterprise!. You must create a Power.Eterprise! tradig parter profile for every tradig parter ivolved i your trasactios, icludig your ow compay. To create a ew tradig parter: 1. Start Power.Maager!. A list of defied istaces of Power.Server! is displayed. 2. Select the istace of Power.Server! to which you wat to coect. (If o Power.Server! coectios are defied, see Coectig to a Server for the First Time opage4-5.) Figure 4-4 Power.Maager! Server Coectio Dialog Box 3. Click Coect. The Power.Maager! mai widow is displayed. 4-8 Usig EDI with WebLogic Itegratio

51 Cofigurig Tradig Parters Figure 4-5 Power.Maager! 4. To set up a tradig parter s compay profile, choose Parters Compay Profiles. The Compay Profile widow is displayed. Usig EDI with WebLogic Itegratio 4-9

52 4 Cofigurig Power.Eterprise! Figure 4-6 Compay Profile List 5. Click New Compay. Eter the required iformatio about your tradig parter. For more iformatio about creatig ad maitaiig tradig parters, see Chapter 4 of the Power.Maager! User Referece Maual. Mappig XML ad EDI Data Oe of the primary goals of Power.Eterprise! is to eable you to maage the traslatio of messages from a stadard data format ito a stadard EDI message format. To do so, you must create maps betwee the data format you have selected ad the correspodig EDI message. These maps are uidirectioal: they operate oly i 4-10 Usig EDI with WebLogic Itegratio

53 Mappig XML ad EDI Data oe directio. Thus, if you eed to be able to traslate data back ad forth betwee a particular XML message format ad a specific EDI message format, you must create two maps: oe for outboud trasformatio (XML to EDI) ad oe for iboud trasformatio (EDI to XML). Fortuately, creatig such maps is ot a difficult task. Power.Map! ca uderstad a variety of stadard documet defiitios, icludig flat files, database tables, XML, ad all the major EDI formats (X12, EDIFACT, ad TRADACOMS). As used withi Power.Map!, a documet defiitio is a elemet-by-elemet descriptio of a documet, its structure, ad the data carried withi it. Thus, you ca use stadard documet defiitios to outlie your maps, the simply coect the idividual data elemets betwee two documet defiitios usig a drag-ad-drop iterface. Figure 4-7 Power.Map! Mai Widow Usig EDI with WebLogic Itegratio 4-11

54 4 Cofigurig Power.Eterprise! For more iformatio about creatig maps, see the Power.Map! User Referece Maual. You may work o maps without beig coected to a Power.Server! istace. If you try to use ay repository commads, however, the Server Coectio dialog box is displayed, requirig you to coect to a server istace so the repository commad ca be ru. To defie a server coectio, see Coectig to a Server for the First Time o page 4-5. At ay time, you ca save a copy of the map you have created o your local system. Choose File Save, the eter a descriptive ame for the map file i the dialog box. The mapisstoredasajarfile. Before you ca use a map i productio, you must promote the map to your server. Select the Fiish tab, the click Promote at the bottom of the tab to sed the map to the server. If you are ot already coected to the server, you must establish a coectio before you ca promote the map. Coectios ad VAN Coectivity Coectios defie how message traffic is delivered, both ito ad out of the Power.Server!. Before you ca use the BEA WebLogic Adapter for Power.Eterprise!, you must cofigure a miimum of four coectios: Source RMI coectio that receives messages from the BEA WebLogic Adapter for Power.Eterprise! Target RMI coectio that seds messages from the Power.Server! to the BEA WebLogic Adapter for Power.Eterprise! Target coectio that seds messages from the Power.Server! to your tradig parter Source coectio that receives messages from your tradig parter Two of these coectios, the source ad target RMI coectios, are used to commuicate with BEA WebLogic Itegratio. These two coectios are used by all EDI trasactios Usig EDI with WebLogic Itegratio

55 Coectios ad VAN Coectivity Creatig RMI Coectios To set up the source ad target RMI coectios: 1. From withi Power.Maager!, select Coectios. The Coectios widow is displayed. Figure 4-8 Power.Maager! Coectios List 2. Create a source RMI coectio. To begi, click Add New. The Create New Coectio dialog box is displayed. Usig EDI with WebLogic Itegratio 4-13

56 4 Cofigurig Power.Eterprise! Figure 4-9 Create New Coectio Dialog Box 3. Set the ame to BEASource, the Trasport to RMI, ad the Directio to Source. Click OK. The Coectio Properties dialog box is displayed. Figure 4-10 Iboud RMI Properties 4. Set Status to Active ad Evelope Recogitio BDD to XMLEvelope. Click OK. 5. Create a outboud RMI coectio. To begi, click Add New. The Create New Coectio dialog box is displayed Usig EDI with WebLogic Itegratio

57 Coectios ad VAN Coectivity 6. Set the ame to BEATarget, the Trasport to RMI, ad the Directio to Target. Click OK. The Coectio Properties dialog box is displayed. Figure 4-11 Outboud RMI Properties 7. Set Status to Active, Target to localhost, adservicenametoedi. Click OK. Creatig Tradig Parter Coectios The other two coectios, the iboud ad outboud tradig parter coectios, are specific to each tradig parter. Therefore, you must defie a uique pair of coectios for each tradig parter. Whe you set up each pair, you must select the trasport that you ad your tradig parter will use. We recommed the followig trasport optios: HTTP: A stadard HTTP/HTTPS trasport protocol for exchagig EDI messages with your tradig parter File: Optio that writes the EDI message to a file, or reads the message from a file. You are resposible for providig a trasport mechaism from this poit i the process. FTP: Optio that uses a FTP server to exchages messages with your tradig parter. Usig EDI with WebLogic Itegratio 4-15

58 4 Cofigurig Power.Eterprise! Get2Coect: A VAN operated by Peregrie Systems. Coectivity to this VAN is icluded with the Power.Eterprise! software, however you must cotact Peregrie Systems to sig up to use the Get2Coect VAN. Use Cleo A+ if you ited to coect via a VAN that requires asychroous commuicatios. For more iformatio, see VAN ad Network Coectivity, i Chapter 2, Architecture. Other coectio optios are also available. For details about all optios, see Chapter 3ofthePower.Maager! User Referece Maual. Cofigurig Exchage Profiles The exchage profile specifies how a tradig parter exchages messages through Power.Server!. Because Power.Server! is a EDI gateway, it is ot the fial poit of receipt for a message. A exchage profile describes how Power.Server! receives a message, trasforms it, ad seds it to its destiatio. For example, a exchage profile might defie the receipt of a EDI message from a tradig parter, its trasformatio ito a XML message, ad its delivery to the BEA WebLogic Adapter for Power.Eterprise!. Exchage profiles caot be created uless certai prerequisite iformatio has bee defied. Specifically, you must have created ad promoted to the server your exchage maps, your tradig parter profile, ad both the source ad target coectios. (The source ad target coectios post messages to Power.Server! ad receive messages from Power.Server!, respectively.) For example, to create a exchage profile that allows you to sed a message to your tradig parter, you eed the followig: XML-to-EDI-trasactio map for the EDI message you pla to sed Your tradig parter profile BEAOutboud RMI coectio you created i Coectios ad VAN Coectivity o page 4-12 Outboud coector to your tradig parter Other iformatio is also required. For details, see Chapter 4 of the Power.Maager! User Referece Maual. For examples of both iboud ad outboud exchage profiles, see Chapter 6, EDI Sample, i this documet Usig EDI with WebLogic Itegratio

59 CHAPTER 5 Cofigurig EDI Itegratio BEA WebLogic EDI Itegratio must be completely cofigured before it ca be used. Because EDI Itegratio depeds o the Power.Eterprise! software to properly operate, you must properly cofigure Power.Eterprise! before you ca commuicate with your tradig parters. Geeral Cofiguratio This sectio discusses the geeral cofiguratio iformatio that you should perform before attemptig to cofigure a specific documet exchage with a tradig parter. Usig EDI with WebLogic Itegratio 5-1

60 5 Cofigurig EDI Itegratio Cofigure Tradig Parters Before cofigurig idividual trasactios, you should cofigure all tradig parters, icludig your ow compay, usig Power.Maager!. For more iformatio about cofigurig tradig parters, see the followig topics: Cofigurig Tradig Parters o page 4-8 Chapter 4, Parters, i the Power.Maager! User Referece Maual Cofigure VAN/Tradig Parter Coectivity You should also cofigure your tradig parter coectivity before attemptig to cofigure idividual documet exchages. See the followig topics: Coectios ad VAN Coectivity o page 4-12 Chapter 3, Coectios, i the Power.Maager! User Referece Maual Although you may ot wat to set up coectivity to your productio tradig parters at this time, you may wat to cofigure them with file coectors for developmet ad testig purposes. Cofigurig EDI Itegratio to Receive a EDI Documet This sectio describes how to cofigure EDI Itegratio so that the BEA WebLogic Adapter for Power.Eterprise! 3.0 ca receive a EDI documet ad sed it to the WebLogic Itegratio process egie as a XML documet. 5-2 Usig EDI with WebLogic Itegratio

61 Cofigurig EDI Itegratio to Receive a EDI Documet Pre-Plaig Determie the EDI stadard, versio, ad documet type that you will receive. For example, you might select a X documet v4010, which is a X12 stadard, 850 type documet, versio Defie the XML format that you will use iterally. This XML format should cotai a complete data map of the fields i the EDI documet that you will use. Create a DTD ad a XSD for the XML documet. You must create both because Power.Eterprise! ad WebLogic Itegratio do ot use the same data file format for this step. WebLogic Itegratio requires a XSD (if you supply oe at all), while Power.Eterprise! requires a DTD. You should ote that Power.Eterprise! does ot provide ay export utility to export a DTD or XSD from a map defiitio oce the DTD or XSD has bee imported. You will be resposible for creatig both the DTD ad XSD files. Withi Power.Eterprise! Create a map betwee the XML documet ad the EDI documet. Import the DTD ito Power.Map! to load the XML documet stadard. The appropriate EDI documet should already exist i the Power.Server! repository. If the EDI documet is ot preset, cotact BEA Customer Support. For more iformatio about how to do this, see the followig topics: l Mappig XML ad EDI Data o page 4-10 l Chapter 3, Maps i the Power.Map! User Referece Maual Defie a iboud coectio. This coectio should use your tradig parter s coectio protocol, which you should have already defied. See Coectios ad VAN Coectivity o page 4-12 for more iformatio. Defie a RMI target coectio. This coectio is used to commuicate with the WebLogic Itegratio process egie. Defie a exchage profile, usig the procedure discussed i Cofigurig Exchage Profiles o page This exchage profile should coect the iboud coectio from your tradig parter to the RMI target coectio. Usig EDI with WebLogic Itegratio 5-3

62 5 Cofigurig EDI Itegratio Withi BEA WebLogic Itegratio Create a applicatio view, usig the procedure i Cofigurig the BEA WebLogic Adapter for Power.Eterprise!. Create a evet for the applicatio view you just created, usig the procedure i CofigurigEvets opage3-7.besuretosetthefollowigparameters: l l l l l Evet Name: The ame of the evet. The ame should be descriptive (for example, ReceivePurchaseOrder) Evet Descriptio: Text descriptio of the evet RMI Service Name: This should match the RMI service ame defied i the Power.Eterprise! RMI target coectio setup i the previous sectio. XSD: The XML schema of the XML message to be received (optioal) XML Root Elemet: The XML root elemet of the XML schema (optioal) Deploy the applicatio view you have created ad defied. Verify that the Power.Server! istace is ruig. At this poit, the applicatio view should be available to the WebLogic Itegratio process egie usig the applicatio itegratio plug-i. For more iformatio about the applicatio itegratio plug-i, see Uderstadig the Applicatio Itegratio Plug-I for BPM i Itroducig Applicatio Itegratio. Note: Always start the Power.Server! before you start WebLogic Itegratio or WebLogic Server. The WebLogic Itegratio coectors expect to see the Power.Server! ruig whe they are iitialized, ad they throw exceptios if Power.Server! is ot ruig whe they are iitialized. 5-4 Usig EDI with WebLogic Itegratio

63 Cofigurig EDI Itegratio to Sed a EDI Documet Cofigurig EDI Itegratio to Sed a EDI Documet Pre-Plaig This sectio describes how to cofigure EDI Itegratio to sed a EDI documet usig a XML documet i the WebLogic Itegratio process egie as the source. Determie the EDI stadard, versio, ad documet type that you will receive. For example, you might select a X documet v4010, which is a X12-stadard, 850-type documet, versio Defie the XML format that you will use iterally. This XML format should cotai a complete data map of the fields i the EDI documet that you will use. Create a DTD ad a XSD for the XML documet. You must create both because Power.Eterprise! ad WebLogic Itegratio do ot use the same data file format for this step. WebLogic Itegratio requires a XSD (if you supply oe at all), while Power.Eterprise! requires a DTD. You should ote that Power.Eterprise! does ot provide ay export utility to export a DTD or XSD from a map defiitio oce the DTD or XSD has bee imported. You are resposible for creatig both the DTD ad XSD files. Withi Power.Eterprise! Create a map betwee the XML documet ad the EDI documet. Import the DTD ito Power.Map! to load the XML documet stadard. The appropriate EDI documet should already exist i the Power.Server! repository. If the EDI documet is ot preset, cotact BEA Customer Support. For more iformatio about how to do this, see the followig topics: l Mappig XML ad EDI Data o page 4-10 l Chapter 3, Maps i the Power.Map! User Referece Maual Defie a outboud coectio. This coectio should use your tradig parter s coectio protocol, which you should have already defied. See Coectios ad VAN Coectivity o page 4-12 for more iformatio. Usig EDI with WebLogic Itegratio 5-5

64 5 Cofigurig EDI Itegratio Defie a RMI source coectio. This coectio is used to commuicate with the WebLogic Itegratio process egie. Defie a exchage profile, usig the procedure discussed i Cofigurig Exchage Profiles o page This exchage profile should coect the RMI source coectio to your tradig parter s outboud coectio. Withi BEA WebLogic Itegratio Create a applicatio view, usig the procedure i Cofigurig the BEA WebLogic Adapter for Power.Eterprise! o page 3-3 i this documet. Create service for the applicatio view you just created, usig the procedure i Cofigurig Services o page 3-10 i this documet. Be sure to set up the followig parameters: l l l l l Service Name: The ame of the service. The ame should be descriptive (for example, SedPurchaseOrder). Service Descriptio: Text descriptio of the service. Coectio Name: This ame should match the RMI service ame defied i the Power.Eterprise! RMI source coectio setup, described i the previous sectio. XSD: The XML schema of the XML message to be set. (optioal) XML Root Elemet: The XML root elemet of the XML schema. (optioal) Deploy the applicatio view you have created ad defied. Verify that the Power.Server! istace is ruig. At this poit, the applicatio view should be available to the WebLogic Itegratio process egie usig the applicatio itegratio plug-i. For more iformatio about the applicatio itegratio plug-i, see Uderstadig the Applicatio Itegratio Plug-I for BPM i Itroducig Applicatio Itegratio. 5-6 Usig EDI with WebLogic Itegratio

65 CHAPTER 6 EDI Sample This sectio describes the cofiguratio ad operatio of the EDI sample. Because the EDI sample relies o the proper cofiguratio of Power.Server!, you must cofigure Power.Server! before you ca ru the sample. (Such cofiguratio is ot a requiremet for ruig the other samples provided with BEA WebLogic Itegratio.) It icludes the followig topics: Sample Overview Settig up ad Ruig the Sample Sample Overview The EDI sample cotais a simple Purchase Order busiess process. Two tradig parters are ivolved: Buyer: Advaced Networks Ic. (ANI) Supplier: Geeral Cotrol Systems (GCS) Advaced Networks buys cotrol system compoets from Geeral Cotrols. ANI uses EDI to sed Purchase Orders to GCS ad to receive Purchase Order Ackowledgmets from Supplier GCS. The Sample is based o the assumptio that Supplier GCS uses BEA WebLogic Itegratio as its Busiess to Busiess Itegratio solutio, that is, as the framework i which it exchages EDI documets with its tradig parters. The architecture of the WebLogic EDI Itegratio is show i the followig figure. Usig EDI with WebLogic Itegratio 6-1

66 6 EDI Sample Figure 6-1 EDI Sample Sceario The EDI sample is based o the assumptio that Supplier GCS uses WebLogic Itegratio as its Busiess to Busiess itegratio solutio for commuicatig with its tradig parters usig EDI. The architecture of the EDI sample is show i Figure 6-2. Figure 6-2 EDI Sample Architecture The sample cosists of a iboud EDI 850 Purchase Order that is received by Power.Server! through a iboud file coectio. The EDI 850 is traslated ito a Purchase Order i XML format ad set to WebLogic Itegratio usig a target RMI Coectio. The XML documet is received by the WebLogic Itegratio EDI Adapter ad set to a sample workflow through the applicatio itegratio plug-i as a applicatio itegratio evet. The sample workflow trasforms the Purchase Order XML documet ito a Purchase Order Ackowledgmet XML documet ad seds it to Power.Server! via the EDI Adapter usig a service call. The service call uses a RMI source coectio to sed the documet to Power.Server!. The Purchase Order Ackowledgmet XML documet is traslated to a EDI 855 Purchase Order Ackowledgmet ad writte to the file system usig a outboud file coectio. 6-2 Usig EDI with WebLogic Itegratio

67 Settig up ad Ruig the Sample Settig up ad Ruig the Sample This sectio lists the prerequisites for executig the BEA WebLogic Itegratio EDI sample ad istructios for ruig it. Prerequisites Before you ru the EDI sample, you must istall all product compoets of BEA WebLogic Itegratio, icludig: BEA WebLogic Server 6.1 BEA WebLogic Itegratio 2.1 Power.Eterprise! 3.0 (icludig Power.Server!, Power.Maager!, ad Power.Map!) Hardware ad OS Requiremets Because the EDI sample is based o the assumptio that you have access, o a sigle machie, to all of the software, icludig Power.Server!, Power.Maager!, ad Power.Map!, the OS istallatio requiremets are more restrictive tha those for a productio eviromet. Miimum memory available: 512 MB OS: Widows NT 4.0 with Service Pack 6 or Widows 2000 with Service Pack 1 Cofigurig the EDI Sample Cofiguratio ad executio of the EDI sample require you to perform the followig steps: Usig EDI with WebLogic Itegratio 6-3

68 6 EDI Sample Step 1: Start Power.Server! Step 2: Start Power.Maager! ad Cofigure Parters Step 3: Start Power.Map! ad Load Maps ad Adapters Step 4: Set Up the Coectios Step 5: Set Up the Exchage Profiles Step 6: Set Up the Workflow Step 7: Deploy the Applicatio View Step 8: Ru the Sample The followig files are available i WLI_HOME/samples/EDISample. Readme.txt WLI_EDI_SAMPLE.pdf XMLEvelope.jar EDI850toPOXML.jar POAckXMLtoEDI855.jar EDISampleWorkflow.jar Edi850.edi Note: Always start the Power.Server! before you start WebLogic Itegratio or WebLogic Server. The WebLogic Itegratio coectors expect Power.Server! to be ruig whe they are iitialized, ad they throw exceptios if Power.Server! is ot ruig whe they are iitialized. Step 1: Start Power.Server! Start Power.Server! by selectig Start Meu Programs Power.It Power.Server!. Wait approximately 10 secods for the server to start. Step 2: Start Power.Maager! ad Cofigure Parters 1. Start Power.Maager! by selectig Start Meu Programs Power.It Power.Maager!. 6-4 Usig EDI with WebLogic Itegratio

69 Settig up ad Ruig the Sample Figure 6-3 Power.Maager! Server Coectio Dialog Box 2. If o servers are listed i the left pae, click Add. Figure 6-4 Power.Maager! Server Add Dialog Box Eter the Server Hostame ad Server Cotrol Port of the EDI Server. Click Add. Usig EDI with WebLogic Itegratio 6-5

70 6 EDI Sample 3. Select the Power.Server! to which you wat to coect ad click Coect. Figure 6-5 Power.Maager! Server Coectio Dialog Box The Power.Maager! mai widow is displayed. 6-6 Usig EDI with WebLogic Itegratio

71 Settig up ad Ruig the Sample Figure 6-6 Power.Maager! 4. Set up the compay profiles. Click Parters, the click Compay Profiles. Usig EDI with WebLogic Itegratio 6-7

72 6 EDI Sample Figure 6-7 Compay Profile List 5. Create a Compay Profile for GCS. Click the New Compay ico. The Compay Properties dialog box is displayed. 6-8 Usig EDI with WebLogic Itegratio

73 Settig up ad Ruig the Sample 6. Add the required iformatio about GCS. Figure 6-8 Compay Properties Dialog Box for a New Compay Profile 7. Create a Compay Profile for AES. Click the New Compay ico. 8. Whe the Compay Properties dialog box is displayed, eter the required iformatio about AES. Step 3: Start Power.Map! ad Load Maps ad Adapters 1. Start Power.Map! by choosig Start Meu Programs Power.It Power.Map!. Usig EDI with WebLogic Itegratio 6-9

74 6 EDI Sample Figure 6-9 Power.Map! Mai Widow 2. Import the map to covert the EDI 850 trasactio to Purchase Order XML. Choose File Import. From the Select Import JAR widow select the followig file: WLI_HOME\samples\edi\EDI850toPOXML.jar 6-10 Usig EDI with WebLogic Itegratio

75 Settig up ad Ruig the Sample Figure 6-10 Import JAR Dialog Box Click Import. Usig EDI with WebLogic Itegratio 6-11

76 6 EDI Sample 3. Ope the EDI850toPOXML map file: choose File Ope Map, the select the EDI850toPOXML map. Figure 6-11 Promotig the Fiished Map 4. Export the resultig map to the Power.Server!. Select the Fiish tab, the click Promote Usig EDI with WebLogic Itegratio

77 Settig up ad Ruig the Sample Figure 6-12 Promotig the Fiished Map 5. Import the map to covert the Purchase Order Ackowledgmet XML to the EDI 855 trasactio. Choose File Import. From the Select Import JAR widow select the followig file: WLI_HOME\samples\edi\POAckXMLtoEDI855.jar Click Import. 6. Choose File Ope Map, the select the POAckXMLtoEDI855 map. 7. Export the resultig map to the Power.Server!. Select the Fiish tab, the click Promote. Select Move Map to Productio ad click OK. Usig EDI with WebLogic Itegratio 6-13

78 6 EDI Sample 8. Import the XML evelope. Choose File Import. Import the followig file: WLI_HOME\samples\edi\XMLEvelope.jar 9. Choose File Ope Documet Defiitio, the select XMLEvelope ad click OK. 10. Export the result to the Power.Server!. Select the Fiish tab, the click Promote. Select Move Doc to Productio ad click OK. 11. You are ow fiished with Power.Map. You ca exit it at this time. Step 4: Set Up the Coectios 1. From withi Power.Maager!, click Coectios Usig EDI with WebLogic Itegratio

79 Settig up ad Ruig the Sample Figure 6-13 Power.Maager! Coectios List 2. Create a RMI coectio from WebLogic Itegratio to Power.Server!. Click the Add New ico. Usig EDI with WebLogic Itegratio 6-15

80 6 EDI Sample Figure 6-14 Create New Coectio Dialog Box 3. Set the ame to WLI_POACK_2_POWERSERVER, Trasport to RMI, addirectioto Source. Click OK. Figure 6-15 Iboud RMI Properties 4. Set Status to Active ad Evelope Recogitio BDD to XMLEvelope, the click OK. 5. Create a RMI coectio from Power.Server! to WebLogic Itegratio. Click the Add New ico Usig EDI with WebLogic Itegratio

81 Settig up ad Ruig the Sample 6. Set the ame to POWERSERVER_2_WLI_PO, Trasport to RMI, addirectioto Target. Click OK. Figure 6-16 Outboud RMI Properties 7. Set Status to Active, Target to localhost, adservicenametopo,theclick OK. 8. Create a iboud file coectio. Click the Add New ico. 9. Set the ame to EDIFILE_2_POWERSERVER, Trasport to File, addirectioto Source. Click OK. Usig EDI with WebLogic Itegratio 6-17

82 6 EDI Sample Figure 6-17 Iboud File Properties Set the followig properties: l Status: Active l Evelope Recogitio BDD: X12 l Directory Path: <WLI_HOME>\samples\edi l Fileame: EDIPurchaseOrder.txt l Do ot set ay other optios. Click OK whe you are fiished. 10. Create a outboud file coectio. Click the Add New ico. 11. Set the ame to POWERSERVER_2_EDIFILE, Trasport to File, addirectioto Target. Click OK Usig EDI with WebLogic Itegratio

83 Settig up ad Ruig the Sample Figure 6-18 Outboud File Properties Set the followig properties: l Status: Active l Directory Path: WLI_HOME\samples\edi l Auto-geerate File Name: Select this optio. l Do ot set ay other optios. Click OK whe you are fiished. Step 5: Set Up the Exchage Profiles 1. From withi Power.Maager!, select Exchage Profiles. Usig EDI with WebLogic Itegratio 6-19

84 6 EDI Sample Figure 6-19 Power.Maager! Exchage Profiles List 2. Set up the iboud EDI exchage profile. Click the Add New ico. The Power.Maager! Exchage Profile Properties widow is displayed Usig EDI with WebLogic Itegratio

85 Settig up ad Ruig the Sample Figure 6-20 New Exchage Profile Dialog Box 3. Set the followig properties: l Map Name: EDI850toPOXML l Source Coectio: EDIFILE_2_POWERSERVER l Target Coectio: POWERSERVER_2_WLI_PO l Profile Status: Active l Parter Compay: AES l Role: Seder l Idetifier: ISASNDR99 Usig EDI with WebLogic Itegratio 6-21

86 6 EDI Sample l O Compliace Error: Reject Documet l Do ot set ay other optios. Click OK whe you are fiished. 4. Set up the outboud EDI exchage profile. Click the Add New ico. 5. Set the followig properties: l Map Name: POAckXMLtoEDI855 l Source Coectio: WLI_POACK_2_POWERSERVER l Target Coectio: POWERSERVER_2_EDIFILE l Profile Status: Active l Parter Compay: AES l Role: Receiver l Idetifier: ISASNDR99 l O Compliace Error: Reject Documet l Do ot set ay other optios. Click OK whe you are fiished. Step 6: Set Up the Workflow Note: If you have executed the Ru Samples setup, as discussed i Preparig to Ru the Samples i Gettig Started, i Ruig the B2B Itegratio Samples, you ca skip Step 6: Set Up the Workflow ad Step 7: Deploy the Applicatio View ad proceed to Step 8: Ru the Sample. 1. Start WebLogic Server: choose Start Programs BEA WebLogic E-Busiess Platform WebLogic Itegratio 2.1 Samples Start Server. 2. Start the WebLogic Itegratio Studio: choose Start Programs BEA WebLogic E-Busiess Platform WebLogic Itegratio 2.1 Start Studio. 3. Log o to WebLogic Itegratio Studio. The default logi for the Samples is: l User ID: joe 6-22 Usig EDI with WebLogic Itegratio

87 Settig up ad Ruig the Sample l Password: password 4. Choose Tools Import Package. 5. Select the file EDISampleWorkflow.jar, located i WLI_HOME\samples\edi. Figure 6-21 Importig the EDI Workflow 6. Select Activate Workflows After Import. If prompted, use Org1. Step 7: Deploy the Applicatio View 1. Start a Web browser. 2. Coect to 3. Log i usig the system logi ID: l ID: system l Password: security Usig EDI with WebLogic Itegratio 6-23