SUN SEEBEYOND eWAY™ HTTPS ADAPTER USER’S GUIDE Release 5.1.
Copyright © 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S.
Contents Contents Chapter 1 Introducing the HTTPS eWay 7 About HTTP and HTTPS 7 About the HTTPS eWay 8 HTTP Messages Web Browser Cookies Cookie Expiration Date Checking GET and POST Methods Sample HTTP Exchange in Client Mode Sample HTTP Exchange in Server Mode 8 8 9 9 9 10 What’s New in This Release 11 About This Document 12 HTTPS eWay Javadoc Scope Intended Audience Text Conventions 13 13 13 13 Related Documents 14 Sun Microsystems, Inc.
Contents Chapter 3 Understanding the HTTPS eWay OTD 22 Overview of eWay OTDs 22 HTTPS Client OTD 22 HTTP OTD Method Descriptions 23 HTTPS Server OTD 23 Chapter 4 Operating SSL 27 Overview 27 KeyStores and TrustStores 29 Generating a KeyStore and TrustStore KeyStores Creating a KeyStore in JKS Format Creating a KeyStore in PKCS12 Format TrustStores Creating a TrustStore Using an Existing TrustStore 29 29 29 31 32 32 32 SSL Handshaking 33 Using the OpenSSL Utility 36 Creating a Sample
Contents Connection Pool Settings 53 Setting Acceptor Threads Property for HTTPS Server Mode 54 Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects 55 eInsight Engine and Components 55 HTTPS eWay With eInsight 56 Server Mode Operation 56 About the HTTPS eWay eInsight Sample Projects 58 Importing a Sample Project 58 Building and Deploying the prjHTTPClient_BPEL Sample Project 59 Project Overview Project Operations Input and Output Data Creating a Project Creating the OTD Creating a
Contents Running the Sample Running the Sample in SSL Mode 93 93 Chapter 7 Implementing the HTTPS eWay JCD Sample Projects 95 About the HTTPS eWay JCD Sample Projects 95 Importing a Sample Project 96 Building and Deploying the prjHTTPClient_JCD Sample Project 96 Project Overview Project Operations Input and Output Data Creating a Project Creating the OTD Creating the Collaboration Definition (Java) Creating a Connectivity Map Selecting External Applications Populating the Connectivity Map Defini
Chapter 1 Introducing the HTTPS eWay Welcome to the Sun SeeBeyond eWay™ HTTPS Adapter User’s Guide. This document includes information about installing, configuring, and using the Sun Java Composite Application Platform Suite HTTPS eWay™ Adapter, referred to as the HTTPS eWay throughout this guide. This chapter provides an overview of Hypertext Transfer Protocol (HTTP) and HTTP over Secure Socket Layer (SSL), better known as HTTPS. This chapter also introduces the HTTPS eWay.
Chapter 1 Introducing the HTTPS eWay Section 1.2 About the HTTPS eWay HTTPS HTTPS (hypertext transfer protocol over secure socket layer—or HTTP over SSL) is a Web protocol that encrypts and decrypts user page requests as well as the pages that are returned by the Web server. HTTP uses port 443 instead of HTTP port 80 in its interactions with the lower layer TCP/IP. SSL uses a 40-bit encryption key algorithm, which is considered an adequate level of encryption for commercial exchange.
Chapter 1 Introducing the HTTPS eWay Section 1.2 About the HTTPS eWay Cookie Expiration Date Checking The HTTPS eWay checks time-limited cookies with expiration dates to ensure that they have not expired. If they have expired, the cookie is removed and is not resent to the originating server. As a result, the session state is removed.
Chapter 1 Introducing the HTTPS eWay Section 1.2 About the HTTPS eWay GET /path/file.html HTTP/1.0 (Request Header Line) User-Agent: HTTP(S)eWay (Request Header field) The server sends a response back through the same socket. The response could look like the following example: HTTP/1.
Chapter 1 Introducing the HTTPS eWay Section 1.3 What’s New in This Release Figure 1 Sample Input Form When the client enters a name in a browser and clicks Submit, the HTTPS eWay server returns a simple response (according to the logic in the Collaboration or Business Process). Figure 2 Sample Response 1.
Chapter 1 Introducing the HTTPS eWay Section 1.4 About This Document Multiple Drag-and-Drop Component Mapping from the Deployment Editor: The Deployment Editor now allows you to select multiple components from the Editor’s component pane, and drop them into your Environment component. Support for Runtime LDAP Configuration: eWay configuration properties now support LDAP key values.
Chapter 1 Introducing the HTTPS eWay Section 1.4 About This Document HTTPS eWay Javadoc An HTTPS eWay Javadoc is also provided that documents the Java methods available with the HTTPS eWay. The Javadoc is uploaded with the eWay’s documentation file (HTTPeWayDocs.sar) and downloaded from the Documentation tab of the Sun Java Composite Application Platform Suite Installer. To access the full Javadoc, extract the Javadoc to an easily accessible folder, and double-click the index.html file. 1.4.
Chapter 1 Introducing the HTTPS eWay 1.5 Section 1.5 Related Documents Related Documents The following Sun documents provide additional information about the Sun Java Composite Application Platform Suite product: Sun SeeBeyond eGate™ Integrator Sun Java Composite Application Platform Suite Installation Guide 1.6 Sun Microsystems, Inc. Web Site The Sun Microsystems web site is your best source for up-to-the-minute product news and technical support information. The site’s URL is: http://www.sun.
Chapter 2 Installing the HTTPS eWay What’s in This Chapter HTTPS eWay System Requirements on page 15 Installing the HTTPS eWay on page 15 ICAN 5.0 Project Migration Procedures on page 17 Installing Enterprise Manager eWay Plug-Ins on page 19 2.
Chapter 2 Installing the HTTPS eWay 2.2.1 Section 2.2 Installing the HTTPS eWay Installing the HTTPS eWay on an eGate supported system Follow the directions for installing the Sun Java Composite Application Platform Suite (CAPS). After you have installed eGate or eInsight, do the following: 1 From the Enterprise Manager’s ADMINISTRATION tab, click on license in the Sun Java Composite Application Platform Suite Products Installed table.
Chapter 2 Installing the HTTPS eWay Section 2.2 Installing the HTTPS eWay 4 For Step 2 of the wizard, click the Add All button to move all installable files to the Include in Install field, then click Next. 5 For Step 3 of the wizard, wait for the modules to download, then click Next. 6 The wizard’s Step 4 window displays the installed modules. Review the installed modules and click Finish. 7 When prompted, restart the IDE (Integrated Development Environment) to complete the installation.
Chapter 2 Installing the HTTPS eWay 2.3 Section 2.3 ICAN 5.0 Project Migration Procedures ICAN 5.0 Project Migration Procedures This section describes how to transfer your current ICAN 5.0.x Projects to the Sun Java Composite Application Platform Suite 5.1.1. To migrate your ICAN 5.0.x Projects to the Sun Java Composite Application Platform Suite 5.1.1, do the following: Export the Project 1 Before you export your Projects, save your current ICAN 5.0.x Projects to your Repository.
Chapter 2 Installing the HTTPS eWay Section 2.4 Installing Enterprise Manager eWay Plug-Ins Before you can deploy the imported Project, the Project’s components must first be “checked out” of Version Control from both the Project Explorer and the Environment Explorer. To “check out” all of the Project’s components, do the following: A From the Project Explorer, right-click the Project and select Version Control > Check Out from the shortcut menu. The Version Control - Check Out dialog box appears.
Chapter 2 Installing the HTTPS eWay Section 2.4 Installing Enterprise Manager eWay Plug-Ins To add plug-ins from the Enterprise Manager 1 From the Enterprise Manager’s Explorer toolbar, click configuration. 2 Click the Web Applications Manager tab, go to the Auto-Install from Repository sub-tab, and connect to your Repository. 3 Select the application plug-ins you require, and click Install. The application plugins are installed and deployed.
Chapter 2 Installing the HTTPS eWay Alert Code Section 2.4 Installing Enterprise Manager eWay Plug-Ins Description User Action HTTPCLIENTEWAY-CONNECTFAILED000002=Failed to prepare the HTTP Client agent for establishing the connection to the HTTP server. Occurs when a socket connection does not exist. Verify that network connectivity is available. HTTPCLIENTEWAY-GETFAILED000004=Failed on HTTP GET request to URL {0}. Occurs when an HTTPS operation is not successful.
Chapter 3 Understanding the HTTPS eWay OTD This chapter provides an overview of OTDs and describes the HTTPS eWay’s Object Type Definition (OTD) structure. What’s in This Chapter Overview of eWay OTDs on page 22 HTTPS Client OTD on page 22 3.1 Overview of eWay OTDs An OTD contains a set of rules that define an object. The object encodes data as it travels through eGate. OTDs are used as the basis for creating a Java-based Collaboration Definition for a Project.
Chapter 3 Understanding the HTTPS eWay OTD Section 3.3 HTTPS Server OTD OTDs have a tree-like hierarchical data structure composed of fields containing methods and properties. The top root element of the OTD is the HTTPClientApplication interface, and the fields underneath contain Java methods. You can use these Java methods to create Business Rules that specify the HTTP message format and invoke messaging to and/or from an HTTP server.
Chapter 3 Understanding the HTTPS eWay OTD Section 3.3 HTTPS Server OTD Figure 4 Input Server Request Node HTTPS eWay Adapter User’s Guide 24 Sun Microsystems, Inc.
Chapter 3 Understanding the HTTPS eWay OTD Section 3.3 HTTPS Server OTD Figure 5 Input Server Response Node Working with the Server OTD Use the OTDs Request and Response nodes to build the logic in your HTTPS Collaborations. The HTTP response is not sent back to the HTTP client until sendResponse() method is called on the HTTP server input OTD. Figure 6 sendResponse() Method It is critical that you use this method to send the response back to the client.
Chapter 3 Understanding the HTTPS eWay OTD Section 3.
Chapter 4 Operating SSL This chapter explains the operation of the Secure Sockets Layer (SSL) feature available with the HTTP(S) eWay. What’s in This Chapter Overview on page 27 KeyStores and TrustStores on page 29 SSL Handshaking on page 33 Using the OpenSSL Utility on page 36 4.1 Overview The use of SSL with HTTP, here called HTTPS, enables HTTP data exchanges that are secure from unauthorized interception from “hackers” or other entities.
Chapter 4 Operating SSL Section 4.1 Overview Figure 8 General SSL Operation: HTTPS Hacker Man-in-Middle Attack: Cannot break secured channel POST / GET HTTP(S) eWay Web Server Response SSL Communication Channel Private TrustStore KeyStore Key Certificate & CA Certificate Chain Trusted CA Certificates This SSL feature is supported through the use of JSSE version 1.0.3. Currently, the JSSE reference implementation is used.
Chapter 4 Operating SSL 4.2 Section 4.2 KeyStores and TrustStores KeyStores and TrustStores As depicted in Figure 8, JSSE makes use of files called KeyStores and TrustStores. The KeyStore is used by the eWay for client authentication, while the TrustStore is used to authenticate a server in SSL authentication. A KeyStore consists of a database containing a private key and an associated certificate, or an associated certificate chain.
Chapter 4 Operating SSL Section 4.2 KeyStores and TrustStores signing request (CSR). The CA is therefore trusted by the server-side application to which the eWay is connected. Note: It is recommended to use the default KeyStore \logicalhost\is\domains\\config\k eystore.jks where is the directory where the Sun Java Composite Application Platform Suite is installed and is the name of your domain.
Chapter 4 Operating SSL Section 4.2 KeyStores and TrustStores This command generates a certificate signing request which can be provided to a CA for a certificate request. The file client.csr contains the CSR in PEM format. Some CA (one trusted by the Web server to which the eWay is connecting) must sign the CSR. The CA generates a certificate for the corresponding CSR and signs the certificate with its private key. For more information, visit the following web sites: http://www.thawte.com or http://www.
Chapter 4 Operating SSL Section 4.2 KeyStores and TrustStores For the following example, openssl is used to generate the PKCS12 KeyStore: cat mykey.pem.txt mycertificate.pem.txt>mykeycertificate.pem.txt The existing key is in the file mykey.pem.txt in PEM format. The certificate is in mycertificate.pem.txt, which is also in PEM format. A text file must be created which contains the key followed by the certificate as follows: openssl pkcs12 -export -in mykeycertificate.pem.txt -out mykeystore.
Chapter 4 Operating SSL Section 4.3 SSL Handshaking \logicalhost\is\domains\\config\cacert s.jks where is the directory where the Sun Java Composite Application Platform Suite is installed and is the name of your domain. The primary tool used is keytool, but openssl is also used as a reference for generating pkcs12 KeyStores. Notice that in the previous section, steps 2 and 3 were used to import two CAs into the TrustStore created in step 1.
Chapter 4 Operating SSL Section 4.3 SSL Handshaking Figure 9 Server-side Authentication Client (eWay) Handshake: Client Hello Server (Web Server) Handshake: ServerHello Handshake: Certificate Handshake: ServerHelloDone Handshake: ClientKeyExchange ChangeCipherSpec Handshake: Finished ChangeCipherSpec Handshake: Finished Dual authentication: This option requires authentication from both the eWay and Web server.
Chapter 4 Operating SSL Section 4.3 SSL Handshaking Figure 10 Dual Authentication Client (eWay) Handshake: Client Hello Server (Web Server) Handshake: ServerHello Handshake: Certificate Handshake: CertificateRequest Handshake: ServerHelloDone Handshake: Certificate Handshake: ClientKeyExchange Handshake: CertificateVerify ChangeCipherSpec Handshake: Finished ChangeCipherSpec Handshake: Finished HTTPS eWay Adapter User’s Guide 35 Sun Microsystems, Inc.
Chapter 4 Operating SSL 4.4 Section 4.4 Using the OpenSSL Utility Using the OpenSSL Utility The OpenSSL utility is a free implementation of cryptographic, hashing, and public key algorithms such as 3DES, SHA1, and RSA respectively. This utility has many options including certificate signing, which keytool does not provide. You can download OpenSSL from the following Web site: http://www.openssl.org Follow the build and installation instruction for OpenSSL.
Chapter 4 Operating SSL Section 4.4 Using the OpenSSL Utility private key and the corresponding certificate for the CA. The certificate is valid for 365 days starting from the date and time it was created. The properties file C:\openssl\bin\openssl.cnf is needed for the req command. The default config.cnf file is in the OpenSSL package under the apps sub-directory. Note: That to use this file in Windows, you must change the paths to use double backslashes. See “Windows OpenSSL.
Chapter 4 Operating SSL Section 4.4 Using the OpenSSL Utility create an initial serial number file used for tracking certificate signing. This certificate will be valid for 365 days. 4 keytool -import -keystore clientkeystore -file client.cer -alias client Enter keystore password: seebeyond keytool error: java.lang.
Chapter 4 Operating SSL Section 4.4 Using the OpenSSL Utility # This is mostly being used for generation of certificate requests. # RANDFILE = .
Chapter 4 Operating SSL Section 4.4 Using the OpenSSL Utility [ req_distinguished_name ] countryName = Country Name (2 letter code) countryName_min= 2 countryName_max= 2 stateOrProvinceName= State or Province Name (full name) localityName = Locality Name (eg, city) 0.
Chapter 5 Configuring the HTTPS eWay This chapter describes how to set the properties of the HTTPS eWay. What’s in This Chapter Creating and Configuring the HTTPS eWay on page 41 Configuring the eWay Connectivity Map Properties on page 41 Configuring the eWay Environment Properties on page 43 eWay Connectivity Map Properties on page 44 eWay Environment Properties on page 46 Setting Acceptor Threads Property for HTTPS Server Mode on page 54 5.
Chapter 5 Configuring the HTTPS eWay Section 5.2 Configuring the eWay Connectivity Map Properties template containing default configuration properties that are accessible on the Connectivity Map. To configure the HTTPS eWay properties: 1 On the Enterprise Designer’s Connectivity Map, double-click the HTTPS eWay icon. Figure 11 Connectivity Map with Components - Client HTTPS eWay The eWay Properties window appears, displaying the default properties for the eWay.
Chapter 5 Configuring the HTTPS eWay Section 5.3 Configuring the eWay Environment Properties Figure 13 Connectivity Map with Components - Server The eWay Properties window appears, displaying the default properties for the HTTPS Server eWay. Figure 14 eWay Properties - Server 5.3 Configuring the eWay Environment Properties The eWay Environment Configuration properties contain parameters that define how the eWay connects to and interacts with other eGate components within the Environment.
Chapter 5 Configuring the HTTPS eWay Section 5.4 eWay Connectivity Map Properties To Configure the Environment Properties: 1 In Enterprise Explorer, click the Environment Explorer tab. 2 Expand the Environment created for the HTTPS Project and locate the HTTPS External System. Note: For more information on creating an Environment, see the “Sun SeeBeyond eGate Integrator Tutorial”. 3 Right-click the External System created for the HTTPS Project and select Properties from the list box.
Chapter 5 Configuring the HTTPS eWay Section 5.4 eWay Connectivity Map Properties HTTPS eWay Configuration Sections Include: HTTP Settings HTTPS Server eWay Configuration Sections Include: HTTP Server External Configuration 5.4.1 Configuring the Connectivity Map HTTPS eWay Properties The HTTPS eWay Properties include parameters used by the external system.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Table 4 HTTP Server eWay—HTTP Server External Configuration Name servlet-url Description Specifies the last path component of the HTTPS server servlet URL. The client uses this URL value to access the server. Required Value A valid URL. The property value must be the servlet name (for example, HttpServerServlet).
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Proxy Configuration on page 48 Security on page 49 Connection Pool Settings on page 53 5.5.1 HTTP Settings HTTP Settings includes the configuration parameters listed in Table 5. Caution: Calling the clear() method in the Collaboration Editor (Java) clears all properties in this HTTP Settings section.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Table 5 Environment Configuration—HTTP Settings (Continued) Name Content Type Description The default Content type header value to include when sending a request to the server. If no value is specified, a default value of application/x-www-formurlencoded is supplied by the eWay. Required Value A valid string. Important: A change of the configuration value will only alter the header value, and not the actual Content type.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Table 6 Environment Configuration—Proxy Configuration (Continued) Name Description Required Value Proxy Port Specifies the port of the HTTPS proxy. This specifies the HTTPS proxy port to which requests to an HTTP server or reception of data from an HTTP server may be delegated to a proxy. This sets the proxy port for secured HTTP connections. A valid HTTPS proxy port. The default is 8080.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Authentication Details for the Authentication settings used for HTTP authentication are detailed in Table 7. Table 7 Environment Configuration—Security, Authentication Name HTTP Username HTTP Password Description Specifies the user name for authenticating the web site specified by the URL. Specifies the password used for authenticating the web site specified by the URL. Required Value A valid user name.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Table 8 Environment Configuration—Security, SSL (Continued) Name Description Required Value JSSE Provider Class Specifies the fully qualified name of the JSSE provider class. For more information, see the Sun Java Web site at: http://java.sun.com/. It is assumed that the provider class is in the runtime classpath. The name of a valid JSSE provider class. The default is com.sun.net.ssl.internal.ssl.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Table 8 Environment Configuration—Security, SSL (Continued) Name Description Required Value KeyStore Password Specifies the default KeyStore password. The password is used to access the KeyStore used for key/certificate management when establishing SSL connections; there is no default. TrustStore Type The TrustStore type of the TrustStore used for CA certificate management when establishing SSL connections.
Chapter 5 Configuring the HTTPS eWay Section 5.5 eWay Environment Properties Additional information Under some circumstances, you can get different Java exceptions, depending on whether you set this property to True or False. This section explains what causes these exceptions. For example, suppose the host name in the URL is localhost, and the host name in the server certificate is localhost.stc.com.
Chapter 5 Configuring the HTTPS eWay 5.6 Section 5.6 Setting Acceptor Threads Property for HTTPS Server Mode Setting Acceptor Threads Property for HTTPS Server Mode Before you run the Java CAPS Logical Host, you must set the Acceptor Threads property for the Sun SeeBeyond Integration Server HTTP listener. This property allows you to set up the correct performance of the HTTPS eWay in server mode.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects This chapter provides an introduction to the HTTPS eWay BPEL components, and information on how these components are created and implemented in a Sun Java Composite Application Platform Suite Project. Sample Projects are designed to provide an overview of the basic functionality of the HTTPS eWay by identifying how information is passed between eGate and supported external systems via HTTPS.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects 6.2 Section 6.2 HTTPS eWay With eInsight HTTPS eWay With eInsight An eInsight Business Process Activity can be associated with the HTTPS eWay during the system design phase. To make this association, select the desired GET or POST operation under the eWay in the Enterprise Explorer and drag it onto the eInsight Business Process Designer canvas.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.2 HTTPS eWay With eInsight Table 10 Receive: Business Rule Designer Output Nodes (Continued) Node Name Description isSecure Gets or sets a boolean indicating whether this message was made using a secure channel, such as HTTPS. method Gets or sets the name of the HTTP method with which this message was made; for example, GET, POST, or PUT. name (WebHeaderList) Gets or sets the name of the current Web header list.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects 6.3 Section 6.3 About the HTTPS eWay eInsight Sample Projects About the HTTPS eWay eInsight Sample Projects The HTTPS eWay HTTPS_eWay_Sample.zip file contains two sample Projects that provide basic instruction on using HTTPS operations in Business Process Execution Language (BPEL). The prjHTTPClient_BPEL sample Project allows you to observe an end-to-end dataexchange scenario involving eGate and the HTTPS eWay.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects 6.5 Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Building and Deploying the prjHTTPClient_BPEL Sample Project The HTTPS eWay client sample Project prjHTTPClient_BPEL demonstrates how the HTTPS eWay processes information from an HTTPS system via an eInsight Business Process. Resulting or confirming information is then written to a text file.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 16 HTTPS eWay Sample Project H T T P (S ) eW ay In b o u n d F ile A p p lic a tio n F ile In , to H T T P , to F ile O ut C o lla b o ra tio n O u tb o u n d F ile A p p lic a tio n The location of input and output files are defined by the File eWay properties. By default, the inbound File eWay reads from c:\temp\input*.txt.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project POST Command: Post_Sample.xml The input data file for the POST command is: POST http://:/examples/servlet/ RequestParamExample firstnameMyFirstName lastnameMyLastName Sample DTD: MultipleData_In.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project The OTD Wizard Selection window appears. See Figure 17. Figure 17 OTD Wizard Selection 2 From the OTD Wizard Selection window, select DTD from the OTD Wizard column. Click Next. 3 From the Include DTDs to Selected List window, browse to the MultipleData_In.dtd located in the sample folder. Click Select. 4 The MultipleData_In.dtd file appears in the Selected DTD Files pane.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 18 Include DTDs to Selected List 5 Click Next. 6 From the Select Document Elements section, select MultipleData_In_website and click Next. The OTD Options screen appears. HTTPS eWay Adapter User’s Guide 63 Sun Microsystems, Inc.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 19 OTD Options 7 From the OTD Options screen, leave all the OTD options unchecked and click Finish. A Message dialog box appears if the OTD is successfully created. The OTD appears in the Project Explorer as the OTD icon MultipleData_In_website. 6.5.4 Creating a Business Process The next step is to create the Project’s Business Process.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 20 Logic of the Business Process Is method is GET or POST? GET POST Execute GET command Name, Value Pair Execute a POST command Copy to print line Send to Collaboration This scenario sets up two possible decisions, called Cases in eInsight. If the inbound file requests a GET operation, it is routed to Case 1.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Table 11 Business Process Cases Case Activity Result Case 1: GET operation Requests that the Business Process get information from the HTTP server. Appropriate information is retrieved. Case 2: POST operation Requests that the Business Process posts information to the HTTP server. Appropriate information is posted.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 21 Business Process Icons: Client 5 By dragging from one icon to another, link the icons on the canvas, as shown in Figure 22. Figure 22 Business Process With Links: Client Two Case icons appear between the Decision Gate and each of your Business Rule icons.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 23 Business Process With Link Business Rules: Client For each Business Rule (Link and Business Rule icon), you must create the settings you want in the Business Rule Designer. 7 Select the Link Business Rule on the left, then click the Map Business Process Attributes icon in the toolbar. The Business Rule Designer pane appears at the bottom of the window.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 24 Business Rule Designer: First Link Business Rule 9 In the same way as you did previously, create additional Link Business Rules, as shown in Figure 25 and Figure 26. HTTPS eWay Adapter User’s Guide 69 Sun Microsystems, Inc.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 25 Business Rule Designer: Second Link Business Rule HTTPS eWay Adapter User’s Guide 70 Sun Microsystems, Inc.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 26 Business Rule Designer: Third Link Business Rule 10 In addition, you must set properties for the Business Rule icon components. Select the desired Business Rule icon component to open the Business Rule Designer (Figure 27).
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 27 Business Rule Designer: Case 1 Business Rule 11 Set properties For the Business Rule icon component for Case 2 by dragging and dropping the nodes, as shown in Figure 28. HTTPS eWay Adapter User’s Guide 72 Sun Microsystems, Inc.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 28 Business Rule Designer: Case 2 Business Rule 12 Double-click the Case 1 (red) icon to set the Decision Gate properties for the cases. The Decision Gate Properties dialog box opens. 13 For Case 1, add a string literal by dragging the icon from the toolbar. Call the literal GET. 14 By dragging the icon from the toolbar, add an EQUAL.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 29 Decision Gate Properties Dialog Box: Case 1 18 For Case 2, add a string literal by dragging the icon from the toolbar. Call the literal POST. 19 By dragging the icon from the toolbar, add an EQUAL. 20 Drag Method under MultipleData_In_with_top_website.unmarshal.Output to any1 under EQUAL in the left pane. 21 Drag POST under string literal to any2.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 30 Decision Gate Properties Dialog Box: Case 2 23 Click Save on the Enterprise Designer toolbar to save your Business Process. After you have finished creating your Business Process, you can use it to define one or more of the eGate Services on your Connectivity Map. 6.5.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Selecting External Applications When creating a Connectivity Map, you can associate any Service, in this case a Business Process, with an external application. For example, to establish a connection to HTTP, you must first select HTTP as the external application to use in your Connectivity Map.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Project Explorer tree onto the Connectivity Map’s HttpBpelService Service icon. If the operation is successfully defined, the gears on the HttpBpelService icon change from red to yellow. Binding the eWay Components The final step in creating a Connectivity Map is binding the eWay components together.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects 6.5.6 Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Creating an Environment Environments include the external systems, Logical Hosts, Integration Servers, and message servers used by a Project and contain the configuration information for these components. Environments are created using the Enterprise Designer’s Environment Editor. 1 From the Enterprise Designer’s Enterprise Explorer, click the Environment Explorer tab.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects 6.5.7 Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Configuring the eWays eWays facilitate communication and movement of data between the external applications and the eGate system. Each Connectivity Map in the The prjHTTPClient_BPEL sample Project use three eWays that are represented as a nodes between the External Applications and the Business Process, as seen in Figure 31.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project 2 Modify the HTTPS eWay Environment properties for your system, including the following settings: HTTP Settings Proxy Configuration Security Connection Pool Settings For further information on configuring the HTTPS eWay, see “eWay Environment Properties” on page 46.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project Figure 34 dpHTTPClient_BPEL Deployment Profile The Project’s components are automatically mapped to their system windows (see Figure 35). Figure 35 dpHTTPClient_BPEL Deployment Profile Automapping 4 Save your current changes to the Repository. 6.5.9 Creating and Starting the Domain To deploy your Project you must first create a domain.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.5 Building and Deploying the prjHTTPClient_BPEL Sample Project 3 If you have already created a domain, select your domain in the Domain Manager and click the Start an Existing Domain button. Once your domain is started, a green check mark indicates that the domain is running. 4 If there are no existing domains, a dialog box indicates that you can create a domain now. Click Yes. The Create Domain dialog box appears.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.6 Building and Deploying the prjHTTPServer_BPEL Sample Project 2 From your output directory, verify the output data. 6.6 Building and Deploying the prjHTTPServer_BPEL Sample Project The HTTPS eWay server sample Project prjHTTPServer_BPEL demonstrates how the HTTPS eWay receives information via HTTP from a server. Resulting or confirming information is then written to a data file.
Chapter 6 Implementing the HTTPS eWay BPEL Sample Projects Section 6.6 Building and Deploying the prjHTTPServer_BPEL Sample Project
