Friday, February 25, 2022

What is Integrated SOA Gateway (ISG) and Integration Repository Customizations

What is Integrated SOA Gateway (ISG)?

Oracle E-Business Suite Integrated SOA Gateway (ISG) is a complete set of service infrastructure to provide, consume, and administer Oracle E-Business Suite Web services. 

You can use this tool to easily discover and search on interfaces, regardless of custom or Oracle seeded ones. 

Major Features of ISG –

Oracle E-Business Suite Integrated SOA Gateway can do the following: 

Display all Oracle E-Business Suite integration interface definitions through Oracle Integration Repository 

Support custom integration interfaces from Oracle Integration Repository 

Provide service enablement capability (SOAP and REST services) for seeded and custom integration interfaces within Oracle E-Business Suite 

Use the Integration Repository user interface to perform design-time activities such as generate and deploy Oracle E-Business Suite Web services 

Support synchronous interaction pattern for REST-based Web services 

Support multiple authentication types for inbound service requests in securing Web service content 

Enforce function security and role-based access control security to allow only authorized users to execute administrative functions 

Provide centralized, user-friendly logging configuration for Web services generated through Oracle E-Business Suite Integrated SOA Gateway's service provider 

Audit and monitor Oracle E-Business Suite inbound service operations from Service Monitor 

Leverage Oracle Workflow Business Event System to enable Web service invocation from Oracle E-Business Suite 

Integration Repository Customizations

Customization of Integration Repository means option to add custom interfaces into Integration Repository.

Interfaces are programs and technologies in Integration Repository, eg. plsql, java, business events, xml gateway etc.

Developers create and annotate custom integration interfaces based on the Integration Repository annotation standards.

Integration administrators use a standalone design-time tool to validate these annotated source files against the annotation standards.

After validation, a loader file is generated and then uploaded to the Integration Repository through backend processing.

These custom interfaces are displayed based on the interface types to which they belong and displayed together with Oracle seeded ones from the Integration Repository user interface.



Post a Comment