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

More documents

Recommendations

Info

Chapter 6: Adapting Imported Services to a Domain Enabling and Updating Sonic ESB Service Containers Once the messaging nodes are established for the connections and endpoints in the target domain, the distributed systems and containers can be implemented. Installing Distributed Systems with Deployment Software On the computer systems that will run the services being deployed, install the appropriate software for the services. For example, the software for ESB requires installing the SonicMQ Container feature and then installing the Sonic ESB Container feature. See Progress Sonic Installation and Upgrade Guide for instructions on all deployment installations. The Sonic Installer requires that you use deployment licenses to install distributed components. Determine what ESB Containers need to be installed from the archive. When you create ESB Containers on distributed systems, the installation creates the named ESB Container and a similarly named management container. The remote installation registers the installation in the Directory Service and creates its boot file. It can run but has no assigned services. Then, when you import the archive, the ESB Container and any associated services and classpaths can overwrite the deployed ESB Container to complete the service configuration. Checking for Elements That Might Not Have Been Exported Chapter 1, “Introduction,” described how deployment archives can package all the files needed to transfer between development domains or move into deployment. Elements that need adjustment in the target domain are: ● Classes External to SonicFS — If you did not import additional classes or JAR files and include them in the deployment package, they must be moved to the deployment domain and relocated in the same relative position to the Sonic installation as they were in the source domain. ● ESBDB Scripts and ESBWS WSDL Files External to SonicFS — ESBDB scripts and ESBWS WSDL files can be stored on a file system outside the Directory Service. When that is the case, these files are not exported by the deployment tool. You can choose to add them into SonicFS as runtime elements. You might need to relocate them in the target domain to the same relative location outside SonicFS in the target domain after importing them. 132 Progress Sonic ESB Deployment Guide 8.5
Enabling and Updating Sonic ESB Service Containers ● GUI Properties Files and Images External to SonicFS — Applications that use graphical components, such as properties files and images, cannot access their files when they are in SonicFS. These files are not exported unless you make a point of doing so. If you do not package them, they must be moved to the deployment domain and relocated in the same relative position to the Sonic installation as they were in the source domain. Tuning the Imported Services Some elements are not bound to configuration objects in a Sonic domain. You could be referencing sample Web locations that will be consistently used in development, staging, and perhaps even in production. References to Files by URL in XSLT Files XSLT files that reference other files in SonicFS must be edited to correct the URL references to appropriate references in the new domain. Endpoints and Services Referenced in Code or in JavaScript Files Endpoints and services that are referenced in application code or in JavaScript files might need to be adapted in the new domain by creating queues. For example, an async dispatch to an endpoint effectively references the endpoint. That means that the destination and connection of that endpoint must exist in the deployment domain. Progress Sonic ESB Deployment Guide 8.5 133
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:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83: 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?