Tuesday, February 15, 2011

Scripting Capabilities

Scripting is commonly used by customers and partners to implement procedural logic or complex business rules within their applications. Customers often have complex business rules pertaining to what are their required fields when a user creates a record. The rule of thumb is always to rely upon configuration to enforce data integrity and entry into a required field wherever and whenever possible. For situations where requirements cannot be met using configuration, developers can turn to Siebel Scripting as an alternative.


1. Business rule definition
2. Perform complex data validations and manipulations
     Which cannot be achieved by declarative configuration
3. Incorporate validations based on internal or external data
     Example: Compare data in different records
4. Dynamic user interaction, for example

  •   Inform user of something
  •   Collect information from user
  •   Custom HTML dialogs
5. Custom behavior definition for user interface controls
     Examples:
  •    Custom menus, buttons, and toolbars
  •    Color coding user interface
 6. Communication with external sources

  •  Desktop applications
  •  Workflow processes
7. Integration solutions
  •  Data transformation
  •  Data sharing
  •  Data transport


Monday, February 14, 2011

Reasons to Avoid Siebel Scripting (music to my ears :))


--Slows processing, Interpreted at runtime

--Introduces potential for data integrity issues and runtime errors

--Requires continued maintenance

--Introduces complexity

--Often reproduces functionality available through configuration

--Complicates upgrade process

Server Scripts vs Browser Scripts:


Server scripts written in eScript and Siebel VB
Interact with database (query, insert, update, delete)
Execute in Object Manager
Limited support for user interaction
Authored in Siebel Tools or in Client
Access to data beyond the current record (validation and manipulation)


Browser scripts written in JavaScript
Interact with users and desktop applications
Download to client and execute in browser
Authored in Siebel Tools
Data validation and manipulation limited to the current record



Thursday, February 10, 2011

Initializing Developer's Local Database

After the Extraction developers must now initialize their local databases. Initialization creates a local database file, called sse_data.dbf and stores it on the developer’s local machine. Siebel Tools includes an initialization program that creates this file.
Steps to initialize a developer’s local database:
1. Open tools put the credentials.
2. Logon and connect to the Local database.

The following message appears:
“The local Siebel database was not found. Would you like to connect to the Siebel Remote server to initialize the local database?”
3. Click Yes.

Siebel Tools connects to the Siebel Remote server and initializes the developer’s local database.
If initialization is successful, the sse_data.dbf file appears in the tools_root\local directory


Performing a Full "Get" Process:

After initializing a local database, you must populate it with a read-only copy of all

the projects and object definitions stored on the server database.
This process is called a full get. A full get is equivalent to checking out all the projects from the
server, however the projects are not locked and you cannot modify the object
definitions until you check out a project from the server database or lock a project
locally.
1.Start Tools , login to Local, tools > Check Out
2. Choose the name of your repository.
3. Select the All Projects radio button.
4. Click the Options button.
5. In the Development Tools Options window, 
 enter Your Server Data Source is pointing to your server development database.
 Your Client Data Source is pointing to the local database you previously
initialized and are currently running against.

These data sources should match those shown in the Control Panel, under ODBC
Data Sources.

6.Close the Development Tools Options
7. In the Check Out dialog box click Get.


After the full get is complete, your currently open local repository has the same
contents as the server repository from which you did the full get.
And now we are ready to check out and do our customization as per the business requirement.

Friday, February 4, 2011

Extracting the Local Database

 1 From the application-level menu, choose View > Site Map > Server Administration > Enterprise Operations.
2 Click the Component Requests tab, and click New.
3 In the Component/Job field, select Database Extract from the pick list.
4 In the Component Request Parameters list, click New and add the necessary parameters.
The required parameter for Database Extract is Client Name.
The value for the Client Name parameter is the name of the mobile Web client say for example MJONES.
5 From the Component Requests menu, select Submit request.
The mobile client database is extracted. This may take 5-10 minutes.

The Database Extract program creates the appropriate directory and its subdirectories for each mobile Web client.
Siebel > docking > MJONES > inbox,outbox
Note : Running the Database Extract task creates a database snapshot for a given user,
which consists of multiple files. These files contain all the data required to initialize
the user’s local client database, and are placed in the directory

serversiebel_srvr_root\docking\user\outbox.

and we are done!!!








Generating a New Database Template

  • A database template is a cached representation of Siebel tables and indexes that are stored in a database file (DBF).
  • You create a database template on the server.
  • Siebel Remote will use the template to create the local database for each developer.
  • You create the database template by running the Generate New Database server component (GenNewDb).
Steps to generate a new database template.

To generate a new database template (GenNewDb) (v7.5.2)

1 From the application level menu, choose View > Site Map >Server Administration >Enterprise Operations.

 2 Click the Component Requests tab.
3 Click New.
4 In the Component/Job field, select Generate New Database.
5 Specify the server name in the Server field.
6 In the Component Request Parameters list, click New.

7 In the Name field, select SQL Anywhere Database from the pick list.
The default value is typically sse_utf8.dbf and appears automatically.
8 From the Components Request menu, select Submit request.
A new database file is generated. This may take a few minutes and the status will show "Success".


Tuesday, February 1, 2011

An error occured executing SQL statement-Siebel:

An error occured executing SQL statement:


When I was trying to access Application's Screen, I was recieving this error. "An error occured executing SQL statement".


Got all the possible reasons. Hope the following post helps.
Possible Reasons and Solutions:

* Invalid column, BC Field without a column, Runtime events are referring to wrong fields etc.

* Spooling by using the command ----> /s "" C:\spool.txt"

run the SQL statement in dbisql and identify the statement that has error associated with it.

Followers

Search This Blog