-
1. Re: deployment of VDB from Ldap sources
rareddy Oct 5, 2015 2:08 PM (in response to prashanthi1)Prashanthi,
Double check for error for creating the resource adapter and data source creation based on it. It must be one of them having an issue. Or you LDAP is not accessible from the new machine .
Ramesh..
-
2. Re: deployment of VDB from Ldap sources
prashanthi1 Oct 5, 2015 3:25 PM (in response to rareddy)Thanks for the reply Ramesh,
The resource adapters in my configuration file were auto created, when i imported the ldap source from jboss studio.
Same configurations i added in the new instance.
do i need to add any other configuration(like datasource) manually to get it working in the new instance?
-Prashanthi.
-
3. Re: deployment of VDB from Ldap sources
rareddy Oct 7, 2015 11:31 AM (in response to prashanthi1)Same configurations i added in the new instance.
Not sure what you added, so that may be an issue.
Typically you need to see the development cycle and deployment cycle differently. For development, you can use Designer to do the auto configuration etc. But when you are taking the VDB into your testing and production environments, you need to exactly know what you are introducing in the configuration.
Typically a VDB, has many data sources. These data sources are either JDBC based connections, or Teiid provided resource-adapters.
If your VDB needs a JDBC based connection.
1) You need to make sure, your JDBC driver is deployed in the server. Either as an module or simply as JAR (if jdbc4 compliant).
2) Then you need to create a data source using the above driver. Typically either editing the standalone-teiid.xml file's "datasources" subsystem, or using the CLI or using the webconsole
If your VDB needs a resource-adapter based connection (LDAP falls into this category)
1) You need to create a "connection-factory" in the "standalone-teiid.xml" by editing the "resource-adapter" subsystem. You can also use CLI for this.
For both scenarios (JDBC, resource-adapter), we provide the example configuration files (for standalone-teiid.xml or CLI) in the "docs/teiid" directory per data source type. Take look at them for an example.
So, make sure you have added the correct configurations with configured names in the VDB, then the issue goes away.
Ramesh..