Using Ensemble as an ESB
Contents
 
   
Server:docs2
Instance:LATEST
User:UnknownUser
 
-
Go to:
Search:    

 
Contents

Preface : 
 
 
Chapter 1: 
 
  • 1.1 Enterprise Service Bus Concepts
  • 1.2 Enterprise Service Bus Architecture
  • 1.3 Configuring an Enterprise Service Bus
  • Chapter 2: 
     
  • 2.1 Summary of the Service Registry Public API
  • 2.2 JSON Description of Services
  • 2.3 Get All Services
  • 2.4 Get Service by ID
  • 2.5 Getting Selected Services
  • 2.6 Getting File Contents
  • Chapter 3: 
     
  • 3.1 Administering the Public Service Registry
  • 3.2 Administering the External Service Registry
  • 3.3 Fields in both the Public and the External Service Registries
  • 3.4 Internal Fields in the Public Service Registry
  • 3.5 Creating and Maintaining a Service Registry Entry
  • 3.6 Searching and Viewing the Service Registry
  • Chapter 4: 
     
  • 4.1 Overview of Configuring Ensemble as an ESB
  • 4.2 Defining Roles and Users for the Public Service Registry
  • 4.3 Configuring a Web Application for the Public Service Registry REST API
  • 4.4 Using the External Service Registry to Configure ESB Hosts
  • Chapter 5: 
     
  • 5.1 Configuring Pass-through Business Services
  • 5.2 Configuring Pass-through Business Operations
  • 5.3 Using SAML Validation in Pass-through Services
  • 5.4 Suppressing Persistent Messages in Pass-through Services and Operations
  • 5.5 Using Other Business Services, Processes, and Operations
  • 5.6 Tracking Performance Statistics of Pass-through Services and Operations
  •  
    Appendix A: 
     
    Appendix B: 
     
    Appendix C: 
     
  • C.1 Using REST Pass-through Services and Operations
  • C.1.1 Pass-through Background Information
  • C.1.2 Pass-through Troubleshooting
  • C.2 Using SOAP Pass-through Services and Operations
  • C.2.1 Calling the External Server from the SOAP Toolkit
  • C.2.2 Adding the SOAP Passthrough Service and Operation
  •  
    Reference A: 
     
  • Sample JSON Return Messages with Registry Entries — Most of the Service Registry public API calls return one or more registry entries. This section describes the format of those entries.
  • Common URL Parameters — The Common URL Parameter ?format is available in most Service Registry public API calls. It controls the line breaks and indenting in the JSON responses. This parameter is available on all Service Registry Public API calls. By default, these calls return JSON with a single space separating each elements and with no line breaks.
  • Get About — Get About lists the public API REST calls that are available.
  • Get File By ID — Get File By ID returns the specified file.
  • Get Services — Get Services shows all services accessible to the user.
  • Get Services By ID — Get Services By ID shows all services accessible to the user that match the specified name, domain, and version.
  • Get Services By Protocols — Get Services By Protocol shows all services accessible to the user that match a protocol in the list.
  • Get Services By Stages — Get Services By Stages shows all services accessible to the user that match a stage in the list.
  • Get Services By Version — Get Services By Version shows all services accessible to the user that match the specified version.
  • Get Services By Word — Get Services By Word shows all services accessible to the user that match the specified search text.
  • Get Services Modified Since — Get Services Modified Since shows all services accessible to the user whose registry entry has been created or updated since the specified date-time.