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

More documents

Recommendations

Info

Chapter 6: Adapting Imported Services to a Domain In the following illustration, the protocol, host, and port defined for the acceptor TCP_ACCEPTOR on the messaging node installed as Broker100 are entered as the Connection URL for the http_defaultConnection ESB connection: The connections defined for ESB endpoints must bind to brokers on ports where the specified connection protocol is supported. You can run analysis reports for SonicMQ dependencies and the impact of the deployment on a domain to reveal the acceptors required by connections. Refer to the following sections: ● “Reporting SonicMQ Dependencies” on page 98 ● “Reporting on SonicMQ Reverse Dependencies” on page 100 ● “Reporting on Impact Analysis” on page 102 126 Progress Sonic ESB Deployment Guide 8.5
◆ To bind connections to host ports in the new domain: Binding ESB Services to Messaging Nodes 1. Connect the Sonic Management Console to the domain that is the import target. 2. On the Configuration tab, expand the broker that you want to use as a messaging node. 3. Click on Acceptors to view the acceptors and their properties. 4. Decide which acceptor you want to use for the ESB endpoint connection. 5. In the ESB Configured Objects section, expand the Endpoints folder and click on SonicMQ Endpoint. 6. Select the Connections tab. 7. Click on each Connection Name to view its parameters. 8. Change the Connection URL to the acceptor you identified in Step 3. You can provide a comma-delimited list of connections. See the SonicMQ Configuration and Management Guide for more about connection lists. 9. Click Apply. 10. Repeat for each connection name as required. The security parameters on the connection for authentication and SSL parameters are discussed in the SonicMQ Configuration and Management Guide. Custom Connections If any connections were defined other than (or instead of) the default ones, you should review them before you start an import to determine whether to allow the import to overwrite existing connection definitions of the same name. Generally, it is a good practice to let individual applications define their own connection names even if they will resolve to the same acceptor used by other connections. The following screen excerpt shows two custom connection definitions: Progress Sonic ESB Deployment Guide 8.5 127
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:
Page 76 and 77: 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?