Cloudscape help please ...

[bobs]

I need to get JBoss 3.0.3 talking to Cloudscape.

From the documentation it seems I need to copy the cloudscape-service.xml (from docs/examples/jca) to the deploy directory and load four Cloudscape jars to (server/default/lib).

However in my version of JBoss (3.0.3) this xml file is not there.

Am I on the wrong track here?

Does anyone have the steps required to get JBoss talking with Cloudscape - and how about the missing cloudscape-service.xmk file!

Help greatly appreciated!

Bobs

[jamesstrachan]

Here are the contents of a Cloudscape-service.xml that I have just deployed. This works on 3.0.4 after a day of headbanging. See forum thread in August for the Security Manager attribute change - which is included here.

<?xml version="1.0" encoding="UTF-8"?>

<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->



<!-- ==================================================================== -->
<!-- ConnectionManager setup for Cloudscape dbms -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- Thanks to Steven Coy -->
<!-- ==================================================================== -->


<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->


DefaultDS



<config-property name="ConnectionURL" type="java.lang.String">jdbc:cloudscape:c:/cloudscape_3.6/databases/business_services</config-property>
<config-property name="DriverClass" type="java.lang.String">COM.cloudscape.core.JDBCDriver</config-property>




<!--Below here are advanced properties -->
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper



<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->


0
50
5000
15
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
ByContainer



<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager

java:/TransactionManager

<!--make the rar deploy! hack till better deployment-->
jboss.jca:service=RARDeployer