About Siebel CRM REST API
REST (Representational State Transfer) is a software architecture style that provides a convenient and consistent approach to requesting and modifying data. In the Siebel CRM RESTful system, resources are stored on the Siebel Server; a client sends a request using an HTTP verb (such as GET, POST, PUT, or DELETE) that the Siebel Server perform a particular action (such as querying, inserting, upserting, or deleting a Siebel CRM resource), and the Siebel Server performs the action and sends a response. The Siebel REST API is provided with the Siebel Application Interface installation. For more information about installing Siebel Application Interface, see Siebel Installation Guide for Microsoft Windows. The Siebel REST API is enabled by configuring and deploying a Siebel Application Interface profile. The Siebel Application Interface profile can be deployed to multiple Siebel Application Interface nodes.
The Siebel REST API exposes Siebel Business Objects, Siebel Business Services, and Siebel Repository Objects. For more information about Siebel Business Objects, Siebel Business Services, and Siebel Repository Objects, see Configuring Siebel Business Applications.
The following are the salient aspects of the Siebel REST API that are aligned with general best practices of REST APIs:
■ A base URI to access Siebel Server resources, for example: http://Server Name:port/Siebel/v1.0/
■ Support for JSON resource representations.
■ Support for XML resource representations.
■ Operations on Siebel CRM resources are mapped to semantically similar HTTP methods, such as GET, PUT, POST, and DELETE.
■ Hypertext links to Siebel CRM Child Business Components in the case of the Data API resources in the REST API response.
■ Support for Outbound to interact with other Cloud applications that communicate through REST.
About Siebel CRM REST API Architecture The Siebel CRM REST API services are deployed as a WAR file on the Siebel Application Interface. The Siebel Application Interface is a java-based Web component that runs on the Tomcat server. The Siebel Application Interface provides the Web entry point to Siebel Business Application services. The Siebel Application Interface interacts with the Siebel Server and Gateway Server to manage and fulfill Siebel REST requests.
Each Siebel Enterprise can have multiple Siebel Application Interface nodes and can have multiple Siebel Servers but can have only one Gateway Server. Installations of Siebel Enterprise Server and Siebel Application Interface modules include deployment of WAR files into the application container and configuration of application container ports. The Siebel application configurations are managed by the Siebel Management Console and stored in the Siebel Gateway Server.
shows the high-level architecture of Siebel REST within the Siebel Application Interface.
■ Requests: Users send an application request to the Siebel Application Interface.
■Siebel Application Interface requests include: UI, EAI, or REST. The appropriate application channel accepts the request. Application channels include: UI Channel, EAI Channel, or REST Channel. n Siebel Application Interface: The Siebel Application Interface serves as the Web server for the Siebel Business Applications. The Siebel Application Interface identifies requests for Siebel application data coming from Web clients and flags these requests for routing to a Siebel Server. When information is sent from the Siebel Server back to the Web client, the Siebel Application Interface helps complete the composition of the Web page for forwarding to the client.
■ Siebel Management Console: The Siebel Management Console is a Web-based application that allows users to configure various Siebel Application components and save the configurations in the Siebel Gateway Server.
■ REST Channel: The REST channel is one of three application channels that provide an endpoint responsible for receiving and processing user requests. The REST Channel is responsible for serving the REST requests. Other application channels include the UI channel and EAI channel.
■ Siebel Server: Siebel Server functions as an application server and is composed of server components.
■ Gateway Server: Siebel Gateway provides the dynamic address registry for Siebel Servers and server components, and also for Siebel Application Interface. The Siebel Application Interface configurations are also stored and managed in the Gateway Server.
■ Outbound Channel: The outbound channel forwards requests to external Web services. For more information, see Siebel Installation Guide for the operating system you are using, Siebel Deployment Planning Guide, and Siebel System Administration Guide.
If you want to know more about it you can follow the below link
https://docs.oracle.com/cd/E88140_01/books/PDF/RestAPI.pdf
Thanks
Happy Learning :)
REST (Representational State Transfer) is a software architecture style that provides a convenient and consistent approach to requesting and modifying data. In the Siebel CRM RESTful system, resources are stored on the Siebel Server; a client sends a request using an HTTP verb (such as GET, POST, PUT, or DELETE) that the Siebel Server perform a particular action (such as querying, inserting, upserting, or deleting a Siebel CRM resource), and the Siebel Server performs the action and sends a response. The Siebel REST API is provided with the Siebel Application Interface installation. For more information about installing Siebel Application Interface, see Siebel Installation Guide for Microsoft Windows. The Siebel REST API is enabled by configuring and deploying a Siebel Application Interface profile. The Siebel Application Interface profile can be deployed to multiple Siebel Application Interface nodes.
The Siebel REST API exposes Siebel Business Objects, Siebel Business Services, and Siebel Repository Objects. For more information about Siebel Business Objects, Siebel Business Services, and Siebel Repository Objects, see Configuring Siebel Business Applications.
The following are the salient aspects of the Siebel REST API that are aligned with general best practices of REST APIs:
■ A base URI to access Siebel Server resources, for example: http://Server Name:port/Siebel/v1.0/
■ Support for JSON resource representations.
■ Support for XML resource representations.
■ Operations on Siebel CRM resources are mapped to semantically similar HTTP methods, such as GET, PUT, POST, and DELETE.
■ Hypertext links to Siebel CRM Child Business Components in the case of the Data API resources in the REST API response.
■ Support for Outbound to interact with other Cloud applications that communicate through REST.
About Siebel CRM REST API Architecture The Siebel CRM REST API services are deployed as a WAR file on the Siebel Application Interface. The Siebel Application Interface is a java-based Web component that runs on the Tomcat server. The Siebel Application Interface provides the Web entry point to Siebel Business Application services. The Siebel Application Interface interacts with the Siebel Server and Gateway Server to manage and fulfill Siebel REST requests.
Each Siebel Enterprise can have multiple Siebel Application Interface nodes and can have multiple Siebel Servers but can have only one Gateway Server. Installations of Siebel Enterprise Server and Siebel Application Interface modules include deployment of WAR files into the application container and configuration of application container ports. The Siebel application configurations are managed by the Siebel Management Console and stored in the Siebel Gateway Server.
shows the high-level architecture of Siebel REST within the Siebel Application Interface.
■ Requests: Users send an application request to the Siebel Application Interface.
■Siebel Application Interface requests include: UI, EAI, or REST. The appropriate application channel accepts the request. Application channels include: UI Channel, EAI Channel, or REST Channel. n Siebel Application Interface: The Siebel Application Interface serves as the Web server for the Siebel Business Applications. The Siebel Application Interface identifies requests for Siebel application data coming from Web clients and flags these requests for routing to a Siebel Server. When information is sent from the Siebel Server back to the Web client, the Siebel Application Interface helps complete the composition of the Web page for forwarding to the client.
■ Siebel Management Console: The Siebel Management Console is a Web-based application that allows users to configure various Siebel Application components and save the configurations in the Siebel Gateway Server.
■ REST Channel: The REST channel is one of three application channels that provide an endpoint responsible for receiving and processing user requests. The REST Channel is responsible for serving the REST requests. Other application channels include the UI channel and EAI channel.
■ Siebel Server: Siebel Server functions as an application server and is composed of server components.
■ Gateway Server: Siebel Gateway provides the dynamic address registry for Siebel Servers and server components, and also for Siebel Application Interface. The Siebel Application Interface configurations are also stored and managed in the Gateway Server.
■ Outbound Channel: The outbound channel forwards requests to external Web services. For more information, see Siebel Installation Guide for the operating system you are using, Siebel Deployment Planning Guide, and Siebel System Administration Guide.
If you want to know more about it you can follow the below link
https://docs.oracle.com/cd/E88140_01/books/PDF/RestAPI.pdf
Thanks
Happy Learning :)
No comments:
Post a Comment