Siebel_系统介绍课件.pptVIP

* eService 8.1 Overview Better UI, better integrated experience, and better technology * * * * What flexibility do you require from an architecture Primary Message: Extensive support across many platforms, channels and deployment configurations – modular architecture minimizes support requirements while delivering high-value, incremental roll-outs Siebel 7 can be deployed in many ways, across many platforms and delivering services across many channels. Enterprise installation backup and recovery Environment Validation Tools Application Deployment Manager Enhanced Mobile Client Deployment End-to-End SSL Standards-based Data Encryption Common Authentication Framework Enhanced Mobile Client Security HTTP Load Balancer support for Siebel Servers Cluster Support Enhanced Documentation * The latest versions of these software components are documented in the Siebel System Requirements and Supported Platforms * Siebel支持的并发用户数是没有限制的，采用N-层体系架构，具有卓越的性能和可伸缩性。系统的可伸缩性可以根据用户数在不同时期的增长需要，分别通过在应用层、数据层无限制地扩展软硬件平台，达到系统负载与处理性能的配备和均衡处理。Siebel 应用服务器本身就可以按照需要，在硬件平台数量不变的情况下，增加配置的数量。Siebel 在支持大量并发用户数方面卓越的、经实践验证的高性能、高可伸缩性和可扩展能力。 * * If you have time show Demonstration No5: Demonstrating integration capabilities by generating XML declaratively using Siebel Workflow * How can Siebel act as a service provider? Just about any business service, application service interface or business process can be published as a service. What is unique about the Siebel service provider model is that we provide a transport neutral publication model. For example, I can publish a business process as a web service and invoke it over a variety of transports – HTTP, MQ, MSMQ, and in 7.7, JMS. The same business process could be invoked via Java, COM, CORBA, or using XML/HTTP, MQ, MSMQ, JMS. There is no one correct approach when invoking a service. The decision as to which approach to use is base primarily on the integration technologies preferred by the customer. The second infl