Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Deployment Planning Guide > Siebel Architecture Overview > About Siebel Internet Session Network APISiebel Internet Session Network API (SISNAPI) is a Siebel proprietary message-body format running on top of TCP/IP. SISNAPI is used for communications between the Web server, Siebel Gateway Name Server, and Siebel Servers. When a client request comes to the Web server, the Siebel Web Server Extension (SWSE) intercepts the request and forwards it in SISNAPI format. The SISNAPI message-body format has the following parts: HTTP HeaderWhen the Siebel Web Server Extension (SWSE) requests a new connection, the initial packets of the first SISNAPI message contain an HTTP header. This header includes a Uniform Resource Locator (URL) that provides routing information to the Siebel Enterprise Server, Siebel Server, and server component. Third-party HTTP load balancers use routing rules to parse the URL and route the message to the correct Siebel Server. Connection MultiplexingSISNAPI TCP/IP connections are specific to an Application Object Manager on one Siebel Server. Before a new connection is opened, the Application Object Manager checks to see whether an existing connection is available. If so, then an existing connection is used. Once the connection is established, it remains open to be used by subsequent messages in the session or to be reused by other sessions. For more information about connection multiplexing, see Siebel Performance Tuning Guide. Transport Layer Security (TLS) or Secure Sockets Layer (SSL)Transport Layer Security (TLS) or Secure Sockets Layer (SSL) encryption and authentication can be configured for SISNAPI connections. For more information, see Siebel Security Guide. See also the Siebel Installation Guide for the operating system you are using. User Request TypesThe Siebel Web Server Extension (SWSE) generates three types of user requests. Each request type creates a new connection to a Siebel Server through the load balancer: initial request, retry request, and reconnect request. The Siebel native load balancing module in the SWSE recognizes these request types and automatically routes them correctly. If you use a third-party HTTP load balancer, then you must configure routing rules to handle these requests.
|
![]() ![]() |
Siebel Deployment Planning Guide | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |