Siebel Client Architecture

7/13/2012 1 Comment

Siebel Web Client, Dedicated and Wireless Client Architecture.

Siebel Dedicated Web Client Architecture

The Siebel Dedicated Web Client connects directly to a database server for all data access, and does not store any Siebel data locally. The Dedicated Web Client runs in a standard browser on the end user's client computer, but does not connect to a Web server. All layers of the Siebel eBusiness Applications architecture, except for the database, reside on the user computer.

Employing this client is not normally recommended for general usage due to the large footprint on the client machine as well as the maintenance overhead. This type of client can be useful in some administration situations, such as when access to the Siebel Enterprise server has been compromised. Such a situation should however be rectified as soon as possible.

Siebel Mobile Web Client Architecture

The Siebel Mobile Web Client is designed for local data access, without the need to be connected to a server. Each mobile machine includes a local database, which the mobile user periodically synchronizes with the Siebel (enterprise) database. The Mobile Web Client runs in a standard browser on the end user's client computer, such as a laptop, but does not connect to a Web server. All layers of the Siebel eBusiness Applications architecture reside on the user computer.

Siebel Remote deployments require careful planning and must be incorporated into the overall design of the Siebel eBusiness application configuration. It is essential to be mindful of the database size and transaction volume that will be placed upon the mobile client as a result of configuration and usage. These will have a significant impact on the overall performance of the Siebel Mobile Web Client and consequently will lead to user adoption problems if these issues are not considered properly.

The subject of deploying Siebel Remote should be covered separately to this document. See also the Siebel Bookshelf document “Remote and Replication Manager Administration Guide” for further details on the architecture and configuration.

Siebel Wireless Client

Siebel eBusiness includes support for WML based wireless devices through optional modules installed at the server side. To support other markup languages a gateway will be necessary since only WML, HTML and XML are currently available in the Siebel eBusiness environment. See the “Siebel Wireless Administration Guide” section “Supporting Wireless Requests with Multiple Markup Languages” for further details.
Additionally, a wireless gateway is required and this is also not part of the Siebel eBusiness distribution.
The application must be configured in the same way as the HTML based version, although a different approach to designing the user interface is necessary.
License keys are available for the following Siebel Wireless applications:

  • Siebel Sales Wireless
  • Siebel Service Wireless
  • Siebel PRM Wireless
  • Siebel Self-Service Wireless

If Siebel Wireless applications are to be accessed through external wireless gateway servers outside of the network firewall, an external IP address must be established. This external IP address can be filtered to allow only certain originating IP addresses, protocols, and ports to enter the enterprise's router.
Related Posts


1 comment :

  1. Thanks for the article. I am new to Siebel and this article provided me a detailed view on architecture

    ReplyDelete

 

Aired | The content is copyrighted and may not be reproduced on other websites. | Copyright © 2009-2016 | All Rights Reserved 2016

Contact Us | About Us | Privacy Policy and Disclaimer