Search This Blog

SBL-EAI-05007: JVM Configuration Section/Named Subsystem not found

Applies to: Siebel Reports - Version:[18393] and later [Release: V7 and later ]
Information in this document applies to any platform.
SymptomsFollowing the migration from the use of the Actuate Report Server to the Oracle BI Publisher Report Server there are a number of changes which need to made to allow the mobile or dedicated client to use reporting functionality.

As the Oracle BI Publisher Report Server has been made available on a number of codelines the installation steps between them may differ depending on the extent of integration available and these steps are documented in the various Maintenance Release Guides.

Following the release of the guides a number of corrections have been identified regarding the installation which have been documented here.

In addition the document may be useful if you are already seeing one of the following types of errors during report execution on a mobile or dedicated client :
JVM Configuration Section/Named Subsystem not found(SBL-EAI-05007)
EAITransport EAITransportDebug 4 0 2010-05-10 10:54:21 Init : com/siebel/data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoundError: com/siebel/data/SiebelPropertySet
ObjMgrBusServiceLog Error 1 0 2010-05-10 10:54:21 (javabsvc.cpp (164)) SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : com/siebel/data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoundError: com/siebel/data/SiebelPropertySet
CauseThese error messages are caused by incorrect or incomplete configuration of the BI Publisher functionality.
SolutionIn order to resolve the aforementioned errors the following information should be reviewed prior to conducting the installation. All of this information relates to the following section in the Maintenance Release Guide (Configuring the Siebel Mobile Web Client to Generate Oracle BI Publisher Reports) :

1) The XMLPJvmSubsys needs to include a reference to the 'DLL' property. This exists as part of the JVMSubsys under normal circumstances and therefore defaults in. If the 'DLL' property does not exist in then the following error will be reported :
JVM Configuration Section/Named Subsystem not found(SBL-EAI-05007)
Create the 'DLL' property as shown below and ensure that the path points to the jvm.dll in the JRE installation on the client machine, for example :
DLL = C:\Progra~1\Java\jre1.6.0_07\bin\client\jvm.dll
2) When copying the XMLPReports and XMLPJvmSubsys into the client .cfg and siebel.cfg files you should ensure that these are placed under the [ActuateReports] section. This will ensure that they are picked up correctly.

3) If the CLASSPATH is copied and pasted from the Maintenance Release Guide into the .cfg file then it will not be correctly retrieved during runtime. This is because the CLASSPATH in the documentation includes carriage returns which will cause the CLASSPATH to be truncated as is evident from the log file on the client :
EAITransport EAITransportGeneric 3 0 2010-05-10 11:02:58 CLASSPATH = C:\sia77\Client_1\classes\SiebelXMLP.jar;C:\sia77\Client_1\classes\
When copying the CLASSPATH ensure that all carriage returns are removed so it is a continuous string. In addition ensure that the full paths are included to the .jar files.
Note : The CLASSPATH in the .cfg has a 500 character limit when being read by the client. Whilst you can enter more than 500 characters in the .cfg file it will be truncated when read by the client.
In any scenario where the client is unable to correctly load the required .jar files it will report the following error :
SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService

In conclusion the complete .cfg file should include the new XMLPReports and XMLPJvmSubsys using the above guidelines resulting in something similar to that shown below :
XdoDir = /xmlp/templates/
ReportOutputDir = /xmlp/reports/
ReportDataDir = /xmlp/data/

FullName = XMLPJvmSubsys
Description = XMLP Java Business Service Subsystem Parameters
SubsysType = JVMSubSys
DLL = C:\Progra~1\Java\jre1.6.0_07\bin\client\jvm.dll
CLASSPATH = C:\sia77\Client_1\classes\SiebelXMLP.jar;C:\sia77\Client_1\classes\xdoparser.jar;C:\sia77\Client_1\classes\xdocore.jar;C:\sia77\Client_1\classes\xmlparserv2-904.jar;C:\sia77\Client_1\classes\jdbc12.jar;C:\sia77\Client_1\classes\bipres.jar;C:\sia77\Client_1\classes\bicmn.jar;C:\sia77\Client_1\classes\siebel.jar;C:\sia77\Client_1\classes\XSLFunctions.jar;C:\sia77\Client_1\classes\SiebelCustomXMLP.jar;C:\sia77\Client_1\classes\SiebelCustomXMLP_SIA.jar
VMOPTIONS = -Xrs -Djava.compiler=NONE

Applies to: Siebel System Software - Version: [18353] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: [18353]
Database: Oracle 9i
Database Server OS: Sun Solaris 7

This document was previously published as Siebel SR 38-1804139878.
SymptomsCustomer was invoking SendReceive method of EAI JMS Transport business service to send a message to WebSphere as a step of a workflow process. When executing the workflow process in Siebel dedicated client, the following error was caused at the step to call the EAI JMS Transport business service:

[1] JVM Configuration/Named Subsystem not found (SBL-EAI-05007)
[2] Error Invoking service 'EAI JMS Transport', method SendReceive at step 'EAI JMS Receive'. (SBL-BPR-00162)

The customer had created a JAVA named subsystem of type JVMSubsys in enterprise profile level already :-
Subsystem Type:

Profile Parameters:
JVM Classpath
JVM Options
M:\CCCDEV_77\siebsrvr\CLASSES\Siebel.jar;M:\CCCDEV_77\siebsrvr\CLASSES\SiebelJI_enu.jar;E:\Program Files\Common Files\IBM\MQM\Java\lib\;E:\Program Files\Common Files\IBM\MQM\Java\lib\;E:\Program Files\Common Files\IBM\MQM\Java\lib\;E:\JNDI-Directory;
E:\Program Files\Common Files\j2sdk1.4.2_04\jre\bin\server\jvm.dll;
-Xrs รข€“Djava.compiler=NONE


Subsystem Type:

Profile Parameters:
ConnectionFactory name
JVM Subsystem name
ReceiveQueue name
Receive timeout
SendQueue name
testQueue file has following entries:
When invoking the method of EAI JMS Transport in Siebel dedicated client, the subsystem [JAVA] should be added in configuration file that is referred by Siebel client application instead of a named subsystem in enterprise profile level. For example, if Siebel client is Call Center application, the subsystem can be defined in uagent.cfg file.
SolutionHere is an example to define the subsystem in configuration file:


DLL = D:\j2sdk1.4.2\jre\bin\server\jvm.dll
CLASSPATH = c:\cp\Siebel.jar;c:\cp\SiebelJI_enu.jar;c:\cp\myJARs.jar;.
VMOPTIONS = -Xrs -Djava.compiler=NONE

For more details, please refer Siebel Bookshelf, Transports and Interfaces: Siebel eBusiness Application Integration Volume III > Java Business Service > Prerequisites for Implementing a JBS.

After adding the [JAVA] subsystem in a configuration (fins.cfg), the error was resolved but the following different error was caused:
[1] Class name incorrect or does not extend SiebelBusinessService : com/siebel/data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoundError: com/siebel/data/SiebelPropertySet(SBL-EAI-05010)
In general, the reported error is caused when Siebel JAR file Siebel.jar and SiebelJI_lang.jar files are not in the CLASSPATH or do not exist in the specified directory. Therefore, the customer had verified the environment variable CLASSPATH entries along with Siebel JVM subsystem and was able to resolve the issue.
Support recommends the following document as a starting point to troubleshooting JMS issues:
NOTE: 850954.1 Basic Troubleshooting Steps for EAI JMS Transport
ReferencesNOTE:850954.1 - Basic Troubleshooting Steps for EAI JMS Transport
NOTE:859382.1 - How to Control Parameters on Transport for Outbound Web Service, e.g. HTTPSleepTime (HTTP) or SendUsername (JMS)


Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software


SBL-EAI-05010; SBL-BPR-00162; SBL-EAI-05007


No comments:

Post a Comment