Siebel 8.1.1.3 plugin

This Siebel product plugin enables integration with and provisioning of Siebel 8.1.1.3 servers.

Prerequisites

An installed Siebel 8.1.1.3 installation (standalone or clustered) on an AIX infrastructure is required if you intend to deploy data and configuration using RapidDeploy.

Usage

This plugin manages the deployment of data and configuration, and control of the Siebel components on target servers.

The configuration used to control the tasks is stored in the Environment product settings. Select the Siebel 8.1.1.3 Environment product and populate the mandatory values. These settings are used to connect, control and configure the Siebel enterprise. There are very little settings needed in most of the Siebel task resources as most of the information is sourced from these environment product settings. When you save the environment configuration, select the check box labelled "Write Environment Data to all Associated Projects:" this will create a file named server.environment.domainxml with all the data set in the environment product in all the projects that references that particular environment.

Task Name Task Description
ImportRepositoryTask This task will encrypt the Siebel passwords using the encryptstring utility and then generates a response file using the ssincfgw utility | to create a master imprep file. This master imprep file is then used to import the Siebel repository using the srvrupgwiz utility.
ChangeNameAndActiveRepositoryTask This task will create a Siebel Java Data bean to connect to the Siebel Server. The connection details are taken from the Siebel  
environment settings. Once a connection is established the "Repository Repository" Siebel Business Object is retrieved to load the  
"Repository Repository" Siebel Businesss Component. The business component data is then searched for Repository with the name "Siebel  
Repository". If this is found it is deactivated and renamed to the backup repository name.  
The imported repository name is then found and activated and renamed to "Siebel Repository".
DeleteRepositoryEntryTask This task will create a Siebel Java Data bean to connect to the Siebel Server. The connection details are taken from the Siebel  
environment settings. Once a connection is established the "Repository Repository" Siebel Business Object is retrieved to load the  
"Repository Repository" Siebel Businesss Component. The business component data is then searched for Repository with the named  
'repositoryNameSearchSpec' resource. If these records are found, they are deleted from the repository. If the repository found has the  
name "Siebel Repository", that record is ignored and not deleted. This task is useful if the ImportRepository task fails and needs to  
be re-run as it leaves the repository records in an invalid state.
DDLSyncTask This task will encrypt the Siebel passwords using the encryptstring utility and then generates a response file using the ssincfgw utility | to create a master ddlsync file. This master ddlsync file is then used to synchronise the DDL using the srvrupgwiz utility.
ExecuteSQLPlusScriptTask This task will use SQLPlus to execute an SQL script against the DB defined in the Siebel Environment.
ExecuteGatewayServerCommandTask This task will execute a Siebel Gateway Name Server command e.g. start_ns or srvredit.
StartGatewayServerTask This task is like the task ExecuteGatewayServerCommandTask except the command is fixed to: start_ns. It will execute a start_ns command  
on the Siebel Gateway Name Server.
StopGatewayServerTask This task is like the task ExecuteGatewayServerCommandTask except the command is fixed to: stop_ns. It will execute a stop_ns command on  
the Siebel Gateway Name Server.
ExecuteSiebelServerCommandTask This task will execute a Siebel Server command e.g. start_server all or cfgedit.
ExecuteSiebelServerGroupCommandTask This task will concurrently execute a Siebel Server command on a group of servers defined in the environment.
StartSiebelServersTask This task is like the task ExecuteSiebelServerGroupCommandTask, except the command is fixed to "start_server all". This task will  
concurrently execute a "start_server all" command on all Siebel Servers defined in the Siebel Environment.
StopSiebelServersTask This task is like the task ExecuteSiebelServerGroupCommandTask, except the command is fixed to "stop_server all". This task will  
concurrently execute a "stop_server all" command on all Siebel Servers defined in the Siebel Environment.
ExecuteSiebelWebServerExtCommandTask This task will execute a Siebel Web Server Extension command.
ExecuteSiebelWebServerCommandTask This task will execute a Siebel Web Server command.
ExecuteSiebelWebServerGroupCommandTask This task will concurrently execute a Siebel Web Server command on a group of servers defined in the environment.
StartSiebelWebServersTask This task will concurrently execute a "startapa" command on all the Siebel Web Servers defined in the Siebel Environment.
StopSiebelWebServersTask This task will concurrently execute a "stopapa" command on all the Siebel Web Servers defined in the Siebel Environment.
ExecuteSiebelServerSrvrMgrCommandTask This task will execute a Siebel Server srvrmgr command e.g. list servers. You can optionally specify an error string to find in the  
output, if the error string if found then a task exception is thrown.
ExecuteSiebelServerSrvrMgrScriptTask This task will execute a Siebel Server srvrmgr script. You can optionally specify an error string to find in the output, if the error  
string if found then a task exception is thrown.
WorkflowBatchComponentTask This task will execute a Siebel Server srvrmgr command based on the input of a configuration file. 
An example of the server manager command based on the input of the properties file: 
 
/srvrmgr /g AIXDEV01 /e En_SblDEMO /u SADMIN /p SADMIN /c "run task for component WfProcBatchMgr server localhost with  
ProcessName="Process ABC",SearchSpec="[Case] IS NOT NULL",TraceFlags=4".
GenerateBrowserScriptsCommandTask This task will run the genbscript to generate the Web javascript files. It will then concurrently copy the generated files onto all the  
Siebel Servers defined in the Siebel Environment. Note: this task will not copy the generated browser scripts onto the host the files  
were generated on, if that host is in the targetServerNames list it will be ignored from the secure copy.
ActivateBulkWorkflowsTask This task will create a Siebel Java Data bean to connect to the Siebel Server. The connection details are taken from the Siebel  
environment settings. Once a connection is established the "Workflow Admin Service" Siebel Service is retrieved to load search for the  
workflows using the search spec. The service will then invoke the "Activate" method on the service and the number of workflows activated  
will be logged out into the log file. This task can activate workflows concurrently on multiple servers using a comma separated list of  
targetSeverNames and a comma separated list of flowSearchSpecs.
DeleteBulkWorkflowTask This task will create a Siebel Java Data bean to connect to the Siebel Server. The connection details are taken from the Siebe  
environment settings. Once a connection is established the "Workflow Admin Service" Siebel Service is retrieved to load search for the  
workflows using the search spec. The service will then invoke the "DeleteDeploy" method on the service and the number of workflows  
deactivated will be logged out into the log file. This task can activate workflows concurrently on multiple servers using a comma  
separated list of targetSeverNames and a comma separated list of flowSearchSpecs.

Attributes and parameters

List and description of all tasks and resources.

Restrictions

This is separately licensed plugin that is not shipped with the framework. Please contact MidVision sales to obtain a copy of this plugin. This plugin interacts with Oracle Siebel software, which may require a separate license.