Installation Note 44423: SAS Shared Services might fail to configure successfully
The following error indicates that the SAS Shared Services were not configured successfully in the SAS® Deployment Wizard. This error appears in the JBoss server.log file.
ERROR [main] - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException:
Invalid bean definition with name 'baseDbType'
defined in ServletContext resource [/WEB-INF/spring-config/data-config.xml]:
Could not resolve placeholder 'biservmid.dbms.type'
at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties
(PropertyPlaceholderConfigurer.java:268)
. . .additional text lines. . .
To correct the problem, complete the following steps:
- Verify that you have a good metadata backup before proceeding.
- Submit the following code with your site-specific details:
options metaserver="host-name"
metaport=8561
metauser="sasadm@saspw"
metapass="password";
data _null_;
length uri propuri propseturi value $255;
nobj=0;
n=1;
rc=1;
rc2=1;
nobj=metadata_getnobj("omsobj:PropertySet?@Name='Environment.Properties'",n,uri);
do while(rc > 0);
rc=metadata_getnasn(uri,"SetProperties",n,propuri);
rc2=metadata_getattr(propuri,"Name",propseturi);
if (rc>0) then put "Name :" propseturi;
rc2=metadata_getattr(propuri,"DefaultValue",propseturi);
if (rc>0) then put "Value:" propseturi;
n=n+1;
end;
run;
- After you submit this code, review the output to determine whether the following name parameter and value entries are missing:
- Name: biservmid.dbms.type
- Value: SAS
- If the parameter and value are missing, add them by submitting the following code with your site-specific details:
options metaserver="host-name"
metaport=8561
metauser="sasadm@saspw"
metapass="password";
data _null_;
length name objid env_uri biservmid_uri $255;
call missing (name, objid, env_uri, bimidserv_uri) ;
nobj=0;
n=1;
nobj=metadata_getnobj("omsobj:PropertySet?@Name='Environment.Properties'",n,env_uri);
put env_uri=;
rc=metadata_newobj("Property",biservmid_uri,"biservmid.dbms.type");
put biservmid_uri=;
rc=metadata_setattr(biservmid_uri,"DefaultValue","SAS");
put 'SetProperty DefaultValue ==> ' rc=;
rc=metadata_setattr(biservmid_uri,"PropertyName","biservmid.dbms.type");
put 'SetProperty PropertyName ==> ' rc=;
rc=metadata_setassn(biservmid_uri,"AssociatedPropertySet","Append",env_uri);
put 'Set AssociatedProperty ==> ' rc=;
run;
- Copy all of the JAR files from the SAS-configuration-directory\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers directory to the JBoss-directoryserver\SASServer1\lib directory.
- Verify that the sas-jms-service.xml file exists in the JBoss-directory\server\SASServer1\deploy\jms directory and that its content is correct, as shown in the following example:
< ?xml version="1.0" encoding="UTF-8"?>
< server>
<!--
| sas-jms-service.xml
| This file defines the SAS Queues and Topics.
|
| You can add other destinations to this file, or you can create other
| *-service.xml files to contain your application's destinations.
-->
<mbean code="org.jboss.naming.LinkRefPairService" name="jboss.jms:alias=SASTopicConnectionFactory">
<attribute name="JndiName">sas/jms/TopicConnectionFactory</attribute>
<attribute name="RemoteJndiName">ConnectionFactory</attribute>
<attribute name="LocalJndiName">java:/JmsXA</attribute>
<depends>jboss:service=Naming</depends>
</mbean>
<mbean code="org.jboss.naming.LinkRefPairService" name="jboss.jms:alias=SASQueueConnectionFactory">
<attribute name="JndiName">sas/jms/QueueConnectionFactory</attribute>
<attribute name="RemoteJndiName">ConnectionFactory</attribute>
<attribute name="LocalJndiName">java:/JmsXA</attribute>
<depends>jboss:service=Naming</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=AlertQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
<attribute name="JNDIName">sas/jms/AlertQueue</attribute>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=WorkflowQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
<attribute name="JNDIName">sas/jms/WorkflowQueue</attribute>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=WorkflowCommandQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
<attribute name="JNDIName">sas/jms/WorkflowCommandQueue</attribute>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=WorkflowEventsQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
<attribute name="JNDIName">sas/jms/app/WorkflowEventsQueue</attribute>
</mbean>
</server>
- Restart SAS Remote Services and JBoss.
Operating System and Release Information
| SAS System | SAS Shared Services | Microsoft Windows Server 2008 for x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2008 | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 for x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft Windows XP Professional | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 Standard Edition | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.2_M2 | | 9.2 TS2M3 | |
| Microsoft® Windows® for x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Enterprise 32 bit | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Enterprise x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Home Premium 32 bit | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Home Premium x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Professional 32 bit | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Professional x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Ultimate 32 bit | 9.2_M2 | | 9.2 TS2M3 | |
| Windows 7 Ultimate x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Windows Vista | 9.2_M2 | | 9.2 TS2M3 | |
| Windows Vista for x64 | 9.2_M2 | | 9.2 TS2M3 | |
| 64-bit Enabled AIX | 9.2_M2 | | 9.2 TS2M3 | |
| 64-bit Enabled Solaris | 9.2_M2 | | 9.2 TS2M3 | |
| HP-UX IPF | 9.2_M2 | | 9.2 TS2M3 | |
| Linux for x64 | 9.2_M2 | | 9.2 TS2M3 | |
| Solaris for x64 | 9.2_M2 | | 9.2 TS2M3 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Installation Note |
| Priority: | medium |
| Date Modified: | 2011-10-04 10:31:33 |
| Date Created: | 2011-09-27 13:22:48 |