Siebel 8.0 Simplified Installation Tasks/Guide for Windows

Hi Friends,

One of the most frequently asked question regarding Siebel is an shortcut summarized document for its installation, to test it out faster.
Well, on other environments, it may not be easy to write a shortcut document, but for Windows Oracle has definitely written one.

You can access this simplified installation document on Oracle Siebel SupportWeb or Metalink 3 by searching for Document ID: 475438.1 or TechNote 688

Enjoy installing Siebel!

Enabling HighInteractivity for PRM Portal (eChannel) in Siebel v7.8 & Siebel v8.0

Enabling HighInteractivity for Partner Portal (PRM Portal, eChannel) is a simple job!
HighInteractivity provides the same functionality as you find in your Sales or Marketing Application with ActiveX Loaded & minimum page refreshes.
By default, Partner Portal runs in StandardInteractivity Mode.

For Siebel CRM v7.8, following are the steps:
1)Browse to your Siebel_Server_Root\bin\enu\
2)Open the scw.cfg
3)Find the section [SWE]
4)Add the following two lines:

HighInteractivity = TRUE
ShowWriteRecord = TRUE

5) Save the file & restart the server to have HighInteractivity on your PRM Portal

Similarly for Siebel CRM v8.0, following are the steps:
1)Browse to your Siebel_Server_Root\bin\enu\
2)Open the scw.cfg
3)Find the section [InfraUIFramework]
4)Add the following two lines:

HighInteractivity = TRUE
ShowWriteRecord = TRUE

5) Save the file & restart the server to have HighInteractivity on your PRM Portal

Keywords: channel portal,crm,crm portal,customer relationship management,e channel,echannel,high interactivity,on demand,partner portal,prm portal,relationship management,siebel,siebel high interactivity,siebel high interactivity framework,siebel high interactivity framework for ie,siebel portal,siebel systems

Error loading dictionary file diccache.dat.(SBL-DAT-60237)

This error is caused due to problem in schema synchronization. The proposed resolution is to run the Database Utilities & perform Schema Synchronization.

After schema synchronization has been done, stop the Siebel Server Service, search & delete the file diccache.dat from the Siebel Installation directory, if present.

Now restart the Siebel Server Service for generation of fresh diccache.dat file.

Keywords: siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SBL-DAT-60237

Oracle Apps - Java Concurrent Program

Writing a Java Concurrent Program

Concurrent Processing provides an interface JavaConcurrentProgram with abstract method runProgram() which passes the concurrent processing context CpContext. The concurrent program developer will implement all of their business logic for a concurrent program in runProgram().
CpContext will have the request specific log and output file input methods. The class name with the runProgram() method will be registered as the java executable file name in the register executable form.

Follow the following generic format to write a Java Concurrent Program…

package oracle.apps.yourpackage.subpackage;

import oracle.apps.fnd.common.Context;
import oracle.apps.fnd.common.VersionInfo;
import oracle.apps.fnd.cp.request.*;
import oracle.apps.fnd.util.*;

public class HelloWorldApp
implements JavaConcurrentProgram{

public void runProgram(CpContext ctx){

//Obtain the reference to the Output file for Concurrent Prog
OutFile out = ctx.getOutFile();

//Obtain the reference to the Log file for Concurrent Prog
LogFile log = ctx.getLogFile();

try{

//To read parameters passed via Concurrent Program
String myName = null;
ParameterList lPara = ctx.getParameterList();
while (lPara.hasMoreElements())
{
NameValueType aNVT = lPara.nextParameter();
if ( aNVT.getName().equalsIgnoreCase("My Name") )
myName = aNVT.getValue(););
}

//Write your logic here

out.writeln("This will be printed to the Output File");

log.writeln("This will be printed to the Log File", 0);

//Request the completion of this Concurrent Prog
//This step will signal the end of execution of your Concurrent Prog
ctx.getReqCompletion().setCompletion(ReqCompletion.NORMAL,  "Completed.");
}
//Handle any exceptional conditions
catch(Exception e){
StackTraceElement ste[] = e.getStackTrace();
for(int i=0; i<ste.length; i++){
log.writeln(ste[i].toString(), 0);
}
}
}
}

Best Practice

As a best practice, use Oracle JDeveloper patched with the following patch number: 6012619. You can download it from Metalink. This patched release of JDeveloper includes all the FND packages and other requisite packages commonly used while writing Java Concurrent Programs. You may use Eclipse, but you will have to manually copy all the packages from Oracle Apps Server to your local machine and give its reference to the project.

Porting Third-Party Libraries

Ask the DBA to place all the requisite third-party libraries under $JAVA_TOP. To make the third-party libraries available to your JCP, follow the steps outlined below to create your Concurrent Program Executable and to create the actual Concurrent Program.

Create Concurrent Program Executable

Path: Concurrent -> Program -> Executable

Create the concurrent program executable, details of which are as follows:

Executable   : HelloWorld
Short Name   : HelloWorld
Application   : Custom Applications
Execution Method  : Java Concurrent Program
Execution File Name         : HelloWorldApp This is your main class file
Execution File Path  : oracle.apps.yourpackage.subpackage

Create the Concurrent Program

Path: Concurrent -> Program -> Define

We are having one concurrent program.

Program  : HelloWorld Java Concurrent Program
Short Name : HELLOWORLDJCP
Application : Custom Applications
Description : Hello World Program
Executable Name : HelloWorld
Executable Method : Java Concurrent Program
Options  : -classpath  /dv00/oracle/product/DEV1110/java:/dv00/oracle/apps/DEV1110/11.5/au/11.5.0/java/appsborg.zip:/dv00/oracle/product/DEV1110/java/thirdParty1.jar:/dv00/oracle/product/DEV1110/java/thirdParty2.jar

Note:- If your JCP does not make use of any Third-Party libraries, then please DO NOT put any entry in the Options.
The Options to be specified must be fully qualified. Use of environment variables will fail the execution of the Java Concurrent Program.

/dv00/oracle/product/DEV1110/java - This is the path to my $JAVA_TOP
/dv00/oracle/apps/DEV1110/11.5/au/11.5.0/java/appsborg.zip - This is the path to my $AU_TOP/java/appsborg.zip
/dv00/oracle/product/DEV1110/java/thirdParty1.jar - This is the JAR reference to my first Third Party Library dependency.
/dv00/oracle/product/DEV1110/java/thirdParty2.jar - This is the JAR reference to my second Third Party Library dependency.

The paths must be set for appropriate environment as specified above and must be separated using a colon “:” without any new-line characters.

Keywords: apps software,concurrent application,concurrent applications,concurrent tutorial,java application,java concurrent program,java concurrent programming,java example,java examples,
java programming,java sample,java sample code,java source code,java tutorial,java tutorial program,oracle resume

Enabling Auto Order Functionality in Siebel v8.0 CRM /Error Code:SBL-APS-00802

Hi Friends,

If you just installed Siebel CRM v8.0 & are facing issues with AUTO ORDER Functionality while using Quotes (Error: SBL-APS-00802), then you need to do some configuration changes before proceeding.

1) Firstly check whether you have all the workflow components enabled on the server
If not, enable the workflow component group.



2)Go to Sitemap>Administration-Server Configuration>Component Definitions>
Query for the component for which you want to enable the Auto Order functionality. Say for e.g. Sales
Now, in the Component Parameters Applet, Query for: 'Order Management - Enable Asse' & set its Value to: 'True'


3)Go Siebel_Server_Installation_Root\siebsrvr\bin\enu
Open the .cfg file for the application which you just enabled the Auto Order Functionality.
Under the '[InfraObjMgr]' add following line:
'AssetBasedOrderingEnabled = TRUE'
Save the file & close.
You need to do similar changes in your Dedicated or Mobile Client cfg's to enable the functionality.



4)Now restart your Siebel Services!
Order of Siebel Service Restart:
1)Stop the Webserver Service
2)Stop the Siebel Server Service
3)Restart Gateway Server Service
4)Start Siebel Server Service
5)Start the Webserver Service

5)Now go to Sitemap>Administration - Business Process>Workflow Deployment
Select All Workflows & click ACTIVATE


6)Now log out of the application & relogin to test your AUTO ORDER Functionality! It should be working now!

Enjoy!

Keywords: autoorder,auto order,siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SBL-APS-00802