esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

More documents

Recommendations

Info

Chapter 6: Adapting Imported Services to a Domain Deployment to a Distributed Staging or Production Deployment When deploying to a distributed deployment environment, consider the following: [ ] Is the domain manager configured? If so, see Progress Sonic Installation and Upgrade Guide. [ ] Are messaging nodes configured? If so, see Progress Sonic Installation and Upgrade Guide. [ ] Are the tools installed on an administrative system? If so, see Progress Sonic Installation and Upgrade Guide. [ ] Are the required deployment products installed for services? If so, see Progress Sonic Installation and Upgrade Guide. [ ] Is there a tailoring rules file for creating a map for this archive for this domain? If so, see “Adjusting Tailoring Rules to Apply When Creating Map Files” on page 67. [ ] Is there a map file for mapping this archive for this domain? If so, see “Applying Tailoring Rules and Creating a Map File for an Archive” on page 73. [ ] What host port or connection list will be used for administrative connections? See “Binding Connections to Host Ports in the New Domain” on page 125. [ ] What HTTP URLs are used by ESB Services deployed as Web Services? See “Binding Connections to Host Ports in the New Domain” on page 125. [ ] What are the acceptors in the new domain? See “Binding Connections to Host Ports in the New Domain” on page 125. [ ] What is the management user and password in the new domain? See “Reconciling Users and Groups to Authentication Domains” on page 131. [ ] Was the pattern of ACLs changed? If so, “Reconciling Endpoint Access and QoP to Authorization Policies” on page 131. [ ] Are there any new queues? If so, see “Binding the Endpoints in the New Domain” on page 128. [ ] Do you want to force overwriting on file matches? If so, “Setting Import Properties for ESB Artifacts into a Domain” on page 107. 124 Progress Sonic ESB Deployment Guide 8.5
Binding ESB Services to Messaging Nodes Binding ESB Services to Messaging Nodes You can import configurations into a domain that consists of only an ESB-aware domain manager. However, a distributed deployment environment typically constrains the domain manager’s messaging traffic to management traffic. Distributed broker installations are assigned to handle message traffic. Setting Up Distributed Messaging Nodes One of the first steps required after importing a deployment archive is binding connections and endpoints defined in ESB services to the new domain’s messaging environment. Often new messaging brokers are defined and deployed to host the connections and endpoints, especially in the initial stages of a distributed rollout. After the brokers are set up and configured, you can bind the connections and endpoints to the domain. See “Installing SonicMQ Messaging Nodes in the Domain” in the Progress Sonic Installation and Upgrade Guide for basic instructions on installing a messaging node. The administrator of the domain can set up broker clusters, fault tolerant brokers, and establish location-specific encryption and activation mechanisms for the deployed messaging nodes. See SonicMQ Deployment Guide for details on broker architectures and topologies. Binding Connections to Host Ports in the New Domain After the messaging nodes are installed, you can bind the ESB connections defined in SonicMQ Endpoints to acceptors on messaging nodes in the new domain. Important When you initially deploy into a new domain, be sure that you bind to connections on brokers in the new domain instead of perpetuating connections to messaging nodes in the source domain. The ESB connections such as http_defaultConnection and jms_defaultConnection are defined once in a domain. If you are hosting ESB services in a domain for the first time, you need to revise the connection URLs of the default ESB connections to the protocol, host, and port for corresponding acceptors set up on the stated host. Progress Sonic ESB Deployment Guide 8.5 125
Page 1 and 2:
® ® PROGRESS® SONIC® Sonic ESB
Page 3 and 4:
the redistribution, if any, must in
Page 5 and 6:
the relevant code modules. All Righ
Page 7 and 8:
OF USE, DATA, OR PROFITS; OR BUSINE
Page 9:
products derived from this software
Page 12 and 13:
Contents Using the Deployment Expor
Page 14 and 15:
Contents Chapter 7: Updating a Revi
Page 16 and 17:
Preface About This Guide This guide
Page 18 and 19:
Preface Progress Sonic Documentatio
Page 20 and 21:
Preface 20 Progress Sonic ESB Deplo
Page 22 and 23:
Chapter 1: Introduction Roles in Re
Page 24 and 25:
Chapter 1: Introduction Developing
Page 26 and 27:
Chapter 1: Introduction ESB Artifac
Page 28 and 29:
Chapter 1: Introduction Different P
Page 30 and 31:
Chapter 1: Introduction 30 Progress
Page 32 and 33:
Chapter 2: Exporting ESB Artifacts
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Chapter 3: Mapping ESB Artifacts to
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75: Chapter 3: Mapping ESB Artifacts to
Page 96 and 97: Chapter 4: Analyzing ESB Artifacts
Page 106 and 107: Chapter 5: Importing Deployment Art
Page 122 and 123: Chapter 6: Adapting Imported Servic
Page 140 and 141: Chapter 7: Updating a Revised Deplo
Page 146 and 147: Chapter 8: Distributed Deployment a
Page 162 and 163: Index ESBWS WSDL files external to
Page 164: Index 164 Progress Sonic ESB Deploy
show all

esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?