Chapter 10. Exposed Direct Connection runtime pattern: generic profile 215
2. Right-click ITSOGood and select Export → EAR file. Enter a destination to
save the EAR file, making sure to name it ITSOGood.ear. Click Finish.
3. Repeat this process for the Manufacturer project, saving the file as
Manufacturer.ear.
10.4 Runtime guidelines
This section takes you through the steps that are involved for configuring the
sample application using the Extended Enterprise Direct Connection pattern.
The following activities are needed to successfully setup and test the sample
application:
Configuring WebSphere Application Server server profiles
Hosting the WSDL files
Installing and configuring the applications
Securing the Application Servers using Global Security
Configuring the Web server for SSL routing
Running and using the Supply Chain application
10.4.1 Solution topology
In order to represent the complete business scenario, the sample application is
divided into four subapplications:
ITSOGood contains the SCMSampleUI, Retailer, Warehouse, and
LoggingFacility services.
Manufacturer, ManufacturerB, ManufacturerC are three individual services,
each packaged separately, and deployed to three different enterprises.
As described in the Product mapping in “Product mapping selected” on
page 176, we use WebSphere Application Server V6.0.2 to host the ITSOGood
and Manufacturer applications, Microsoft .NET to host the ManufacturerB
application, and CICS Transaction Server to host the ManufacturerC application.
This arrangement is shown in Figure 10-40 on page 216.
Important: Any described port number in this chapter and the following ones
should be translated to the local equivalent in your scenario implementation.
For instance, port 9080 used in some of our URLs might not necessarily be
the HTTP Transport port in your scenario. Rather, your port number might be
9081 instead. The same concept of localized translation applies to hostnames
and IP addresses as well.
216 Patterns: Extended Enterprise SOA and Web Services
Figure 10-40 Solution topology
The runtime guidelines in this chapter describe how to prepare WebSphere
Application Server profiles for the ITSOGood and Manufacturer applications, and
the HTTP server. The guidelines describe how to configure these profiles to use
the WS-Security integrity and confidentially settings that we defined in the
development guidelines.
Optionally, you can implement the ManufacturerB and ManufacturerC
applications as well. To do this you will need access to a Microsoft .NET server
and a CICS Transaction Server V3.1 region. The connection between the
ITSOGood applications and the ManufacturerB and ManufacturerC applications
will not be secured using WS-Security settings in this sample (although in a
production environment this should be configured too).
Instructions for configuring the ManufacturerB and ManufacturerC servers are
described in:
Note: You do not need to configure the ManufacturerB and ManufacturerC
servers to build a working end-to-end sample application.
WebSphere
Application Server V6
ITSOGoodProfile - server1
ITSOGood
Application
ManufacturerProfile - server1
Manufacturer
Application
WebSphere
Application Server V6
ManufacturerB
Application
Microsoft .NET
ManufacturerC
Application
CICS Transaction
Server V3.1
IBM HTTP
Server V6
SSL
pass-through
rules
SOAP / HTTPS
Message
Chapter 10. Exposed Direct Connection runtime pattern: generic profile 217
Appendix B, “Microsoft .NET Web services” on page 483
Appendix C, “CICS Transaction Server Web services” on page 513
10.4.2 Configuring WebSphere Application Server profiles
This section describes how to create server profiles for the ITSOGood and
Manufacturer servers. It assumes the use of WebSphere Application Server
V6.0.2, and that you have this product already installed.
Because this scenario describes an extended enterprise scenario, these two
profiles should, in theory, be located on physically different machines, in different
organizations, and connect using the internet. However, for the purposes of this
sample, both profiles can be installed on the same physical machine with the
same network address. The instructions assume that a single machine is used,
but these instructions can equally be applied to a real extended enterprise
scenario.
Creating the ITSOGoodProfile
The ITSOGoodProfile server profile will be used to host the ITSOGood
enterprise application. This correlates to the Exposed Direct Connection pattern
generic profile product mapping as indicated by the circle in Figure 10-41.
Figure 10-41 ITSOGoodProfile in the Exposed Direct Connection product mapping
To create a WebSphere Application Server profile for use by the ITSOGood
application, perform the following steps on the machine with WebSphere
Application Server V6.0.2 installed:
Inter-enterprise
Zone
Enterprise
Demilitarized Zone Enterprise Secure ZonePartner Zone
App Server/
Services
App Server/
Services
Network
Infrastructure
Protocol FirewallProtocol Firewall
Connector
App Server/
Services
App Server/
Services
Domain FirewallDomain Firewall
Exposed
Connector
Rules
Directory
App Server/
Services
Microsoft .NET
WebSphere
Application
Server V6.0.2
CICS
Transaction
Server V3.1
IBM HTTP
Server V6
Internet
WebSphere
Application
Server V6.0.2
(SOAP
provider)
WebSphere
Application
Server V6.0.2
WebSphere
Application
Server V6.0.2
WebSphere
Application
Server V6.0.2
Directory
& Security
Services
WebSphere
Application
Server V6.0.2
Get Patterns: Extended Enterprise SOA and Web Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
