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

More documents

Recommendations

Info

Chapter 8: Distributed Deployment at Runtime Multiple ESB Containers in a Management Container A management container can support multiple ESB Containers. You might want to do this to have one classloader for the two ESB containers. This tactic is not typically recommended because the memory requirements for another management container’s JVM are minimal when compared to the ESB processes. An appropriate use-case for this construct is when you have a large ESB process that is running intra-container, as shown: Directory Service Management Node esbHostA1 ctHostA esbHostA2 esbHostA1 esbHostA2 Management Container aHost-1 ctHostA SonicMQ In this illustration, HostA has one management container, hosting two ESB Containers. When intra-container steps are in separate ESB Containers, the process writes the message to the broker at strategic places in the process. Thus, a restart of the process can resume the process, and avoid having to start it from its beginning. 152 Progress Sonic ESB Deployment Guide 8.5 HostA ESB Container Sonic ESB Enterprise Service Bus ESB Container Sonic ESB
Multiple Management Containers on a Host Multiple Management Containers on a Host Using multiple management containers provides independence of services. Unless the services complement each other or can use intra-container messaging, it is usually better to use separate container instances, as shown: Directory Service Management Node ctHostA1 ctHostA2 Management Container Management Container SonicMQ aHost-1 ctHostA1 SonicMQ ctHostA2 In this illustration, HostA has two management containers, each hosting an ESB Container. When you keep multiple management containers in the same version, you can use Activation Daemons to provide remote and scheduled startup of management containers. Progress Sonic ESB Deployment Guide 8.5 153 HostA ESB Container Sonic ESB Enterprise Service Bus esbHostA1 esbHostA2 ESB Container Sonic ESB
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:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Chapter 4: Analyzing ESB Artifacts
Page 98 and 99:
Page 100 and 101:
Page 102 and 103: Chapter 4: Analyzing ESB Artifacts
Page 104 and 105: 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 ...

Create successful ePaper yourself

Delete template?

Save as template?