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

More documents

Recommendations

Info

Chapter 6: Adapting Imported Services to a Domain 6. If the JMS Destination Type is Queue, determine whether that queue exists on the target broker. If it does not exist, click Create Queue. 7. Choose the broker from the list of brokers defined for connections. The queue is configured on the broker you select. Click OK. 8. Repeat for each endpoint name as required. The security parameters on the destination for authorization and QoP are discussed in “Reconciling Endpoint Access and QoP to Authorization Policies” on page 131. Routing Nodes When WSDL definitions have routing definitions that use the node syntax (such as sonic://NodeB/Q1), you might have to establish the routing definition in the new domain. You could either revise the WSDL to use a different syntax or to create the node definition in the new domain. While the node does not have to be in the new domain, be sure that it is in the correct context for the new domain; that is to say, if the node was defined as another Workbench in development and you are moving into advanced staging, the node should be redefined as a node in the advanced staging or production infrastructure. 130 Progress Sonic ESB Deployment Guide 8.5
Updating Security Updating Security Security in a domain has a set of interdependencies that make it an important aspect of the initial creation of a domain and messaging nodes. You should plan what security you will use and implement the plan as you define the domain and messaging nodes. There are many aspects of security to consider: ● When you use authentication, you must: ■ Consider whether to use external authentication and the login SPI. ■ Create the users and passwords in the default authentication domain, or use a different authentication domain. ■ For SSL, configure the provider, acceptors, and—if you use certificates—the certificate management and certificate revocation lists. ● When you use Quality of Protection, the cipher suite for encryption ● When you use authorization, defining authorization policies See the SonicMQ Deployment Guide section on implementing security in a domain. Note Channel Encryption and External Authentication — See the SonicMQ Deployment Guide and the SonicMQ Configuration and Management Guide for details about SSL parameters, HTTPS, QoP, and the Login SPI. Reconciling Users and Groups to Authentication Domains SonicMQ endpoint connections specify a user and password. You must either create the user and password information in the target domain or change the ESB connection user and password to one that exists in the target domain. Reconciling Endpoint Access and QoP to Authorization Policies Access control and Quality of Protection (QoP) is enforced by authorization policies in the target domain. Unless you set up patterns that will apply appropriate policies to new queues, topics, and routings, you must modify the ACLs in the target domain to provide your preferred pattern of permissions. Progress Sonic ESB Deployment Guide 8.5 131
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: 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 ...

Create successful ePaper yourself

Delete template?

Save as template?