Each authentication-related parameter in an application's configuration file is interpreted by the security adapter for database authentication. For more information, see the descriptions for equivalent parameters applicable to Siebel Web Client and other authentication contexts, in Siebel Gateway Name Server Parameters. For more information, see Configuring Checksum Validation. Some parameters apply only in a Web SSO authentication environment. For more information, see the descriptions for equivalent parameters applicable to Siebel Web Client and other authentication contexts in Siebel Gateway Name Server Parameters.
Use the encryptstring utility to generate the encrypted value of the ApplicationPassword parameter. For information on using the encryptstring utility, see Encrypting Passwords Using the encryptstring Utility. Configuration file on the Siebel Server. For example, eservice. This requires that you have a certificate from a certificate authority on the Web server on which the Siebel Web Engine is installed.
Specifies the security adapter mode. For database authentication, specify DB. DB is the default value for SecAdptMode. Specifies the name of the security adapter. For database authentication, specify DBSecAdpt. You must add the applicable section to the file yourself. The Siebel application applies transactions while the user accesses the server database through this Siebel application. Set the DockTxnsPerCommit parameter to a low value to prevent locking out other users while Siebel Remote merges transactions.
This parameter contains the name of the computer where you install the Siebel Server software and where you extract the remote client. Make sure you set the DockConnString parameter before you initialize the remote client. You must use the following format when you set the DockConnString parameter:. The following examples are valid values for the DockConnString parameter:.
If you do not include an element, then you must include adjacent colons. For example, the following example does not include the network protocol element:. You can modify the default value of the port number that you specify in the DockConnString parameter. You can also specify this port number as a command line option when you start the Siebel Server. For more information, see Locating the Record for a Server Component. For more information, see Modifying the Siebel Configuration File.
It is recommended that every synchronization occur within the corporate firewall. If your deployment must support synchronization to the Internet from outside the firewall, then it is recommended that you use a VPN Virtual Private Network.
If there is a firewall on the network between the remote client and the Siebel Server, or between the VPN Server and the Siebel Server, then the port for synchronizing with the Siebel Server must be opened on the firewall, and this port must be a port other than port If you do not use a VPN connection, then it is possible that your Internet Service Provider ISP or another host on the router could block communication on the port that you specify for synchronizing.
You can configure the sort order for the local database or for the sample database. For example, locate siebel. For optimal performance, it is recommended that you set the SortCollation parameter to Binary. For more information, see Siebel System Administration Guide. Table 8. This file includes default values for each configuration parameter: bin Siebel Remote reads the configuration parameters from the configuration file that the Windows shortcut specifies for the remote client or for the synchronizer, depending on whether the user starts synchronization while using the remote client or uses the stand-alone synchronizer.
To modify the Siebel configuration file Locate, and then open the configuration file in a text editor. Set the DockRepositoryName parameter. This roadmap provides a typical guideline that describes how to configure a Siebel application.
The actual tasks you perform and the sequence that you use to perform them varies significantly depending on your implementation requirements. Developing a Configuration Strategy. This task is a step in Roadmap for Configuring a Siebel Application. Perform a thorough business analysis that details the needs of your organization and users. Determine whether a predefined Siebel application can or cannot meet the needs of your users.
If a predefined Siebel application cannot meet the needs of your users, determine what business needs require modifications to the Siebel application. An entity relationship diagram ERD or text that describes the entity relationships. For more information, see Using the Entity Relationship Designer.
The names and descriptions of the business objects and business components that Siebel CRM requires, and how they relate to one another.
Screen flow diagrams and a list of fields that Siebel CRM displays on each applet. Conditional How your implementation will use various Siebel technologies. Describe naming formats the development team must use. For more information, see Guidelines for Naming an Object.
Describe how file versions for the physical user interface layer are controlled. Describe how your organization will test and deploy Siebel CRM to users. The complete stepwise procedures your development and test team must follow to complete Siebel CRM configuration.
For more information, see Developing a Configuration Strategy. The major goal of configuring Siebel CRM is to develop an application that meets the look, feel, and requirements of your organization and your users, and that is easy to maintain and upgrade.
Use predefined Siebel application functionality. Create a new object only if you cannot modify a predefined object to meet your requirements. If you follow this principle, then your Siebel application is much easier to maintain and upgrade to future Siebel product releases.
For more information, see Reusing Predefined Objects. Achieve acceptable system performance. For more information, see Siebel Performance Tuning Guide. Build a consistent and intuitive Siebel client. For example, if you create a new form applet, then make sure it uses the same look and feel as other form applets in your Siebel application. Develop a plan to configure Siebel CRM starting at the lower level and working upward:.
This configuration helps you to make sure the correct values for all required object properties are available as options. For more information, see About the Siebel Object Architecture. Assign a development role to a single developer or group. This configuration allows different groups to work in parallel. For example, one group or an individual person can develop a Web page and the logical business object definitions and data object definitions that are required to support the page.
Use a web template. It requires each group to complete some work before another group begins their work. This topic describes how to manage modifications that your development team makes to the physical user interface.
You do not configure the physical user interface layer in Siebel Tools, so you cannot use the Siebel Tools check out and check in feature to manage web templates, JavaScript files, or style sheets. These files are part of the physical user interface layer. If multiple developers simultaneously modify these files, then follow the recommendations that this topic describes.
The description in this topic is appropriate for most projects. For more information, see Getting Help From Oracle. Assign a single developer or group to manage web templates, JavaScript files, and style sheets.
Make sure all modifications are made by this individual or group, who is solely responsible for releasing amended files to the Siebel Web Server environment. Use version control software to manage modifications to web templates, JavaScript files, and style sheets.
ClearCase is an example of source control software. This configuration makes sure that only a single individual amends these files at any time. It provides an audit trail of modifications. If source control software is not available, then use manual controls that allow a structured release.
Assign an individual or group that is responsible for all amendments to physical user interface files and their subsequent release. Use a separate directory structure for each release that includes subfolders for the various objects that are released.
Copy all amended physical user interface files that are included in the release to the appropriate subfolder. The date on which a file is amended can identify the web templates or JavaScript library files that you must release to users. It is necessary to use central release folders or to copy modified or new objects to these folders. A web template is an example of a modified or new object.
This topic summarizes the development process for Siebel CRM and provides information about setting up the development environment. It includes the following information:. Overview of the Development Process. Guidelines for Developing a Siebel Application. This topic describes a summary of work you perform to develop a Siebel application. Developing a Siebel application is not necessarily a serial process.
During some phases, it makes sense for you to configure multiple sections of Siebel CRM concurrently. Some tasks are iterative, such as testing and debugging, so it is likely that you will modify the simplified and linear task that this topic describes so that it meets the development requirements for your team.
Most of the topics in Using Development Tools and Setting Up the Development Environment describe tasks that you can perform to set up a development environment. See also Using Siebel Tools. For more information, see Using Siebel Tools.
Use the tools that are available to you in the Siebel development environment to define whatever assignment and workflow rules are required. For more information, see Localizing Siebel Business Applications. Iterate through the development steps until your design is fully implemented, and until Siebel CRM runs smoothly and meets your performance objectives. This topic describes some guidelines for developing a Siebel application.
For more information about some of these points, see Localizing Siebel Business Applications. Use an object name that is meaningful and descriptive. Do not use a license key option as an object name. For example, do not use Product Forecasting. This configuration can cause Siebel CRM to not display a user interface object, such as a view. Prefix the name for each custom object that you create with your company name.
This configuration distinguishes your custom object from a predefined object. Be careful with spelling, spacing, and capitalization when you name an object. Typically, the logical name of an object in the Siebel repository uses complete words, mixed casing, and a space between words. A physical database object might use an abbreviation, uppercase, and an underscore. Do not use a reserved SQL word in an object name.
This configuration can cause unpredictable application behavior. Avoid modifying the name of an object. It is time consuming to modify the name of an object when Siebel CRM references it throughout the Siebel repository. If you must modify the name of an object, then use the Find in Repository feature from the Tools menu in Siebel Tools to find all of the references. If you attempt to use objects from another character set, then Siebel Tools displays a unique constraint error.
0コメント