Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
16 replies
Subscribers
7 subscribers
Views
6302 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Trying to configure datasource for JS 7 and mssql. I did: 1. modify mo
terryc
over 11 years ago
Trying to configure datasource for JS 7 and mssql.
I did:
1. modify module.xml
<module xmlns="urn:jboss:module:1.0" name="com.microsoft.sqlserver.jdbc">
<resources>
<resource-root path="sqljdbc4.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
2. delete the dataspurce section in standalone.xml (not deleteing it gave me duplicated resources
3. modify appian-ds.xml
<datasources
xmlns:xsi="
www.w3.org/.../XMLSchema-instance"
xsi:noNamespaceSchemaLocation="
www.jboss.org/.../datasources_1_0.xsd">
<xa-datasource jndi-name="jdbc/AppianPrimary" pool-name="AppianPrimary" use-java-context="false">
<xa-datasource-property name="URL">
jdbc:sqlserver://myservername:1433;databaseName=APPIAN_DEV;integratedSecurity=true
</xa-datasource-property>
<driver>com...
OriginalPostID-69855
OriginalPostID-69855
Discussion posts and replies are publicly visible
0
terryc
over 11 years ago
....microsoft.sqlserver.jdbc</driver>
<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<xa-pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>100</max-pool-size>
</xa-pool>
<timeout>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>5</idle-timeout-minutes>
</timeout>
</xa-datasource>
</datasources>
appian-ds.xml deploy fine.
but gotten
javax.naming.NameNotFoundException: jdbc/AppianPrimary -- service jboss.naming.context.java.jdbc.AppianPrimary
Did I missing any step?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alex Weller
Appian Employee
over 11 years ago
Terry, how is your Primary DS defined in custom.properties?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
terryc
over 11 years ago
In customer.properties
conf.data.primary.datasource=@conf.data.datasources.primary.jndiname@
in environment specific build.xml
#conf.data.datasources.primary.jndiname=java:/jdbc/AppianPrimary
#conf.data.datasources.primary.host=myservername
#conf.data.datasources.primary.port=:1433
#conf.data.datasources.primary.instance=
#conf.data.datasources.primary.databaseName=APPIAN_DEV
#conf.data.datasources.primary.integratedSecurity=true
#conf.data.datasources.primary.username=
#conf.data.datasources.primary.password=
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alex Weller
Appian Employee
over 11 years ago
What version of Appian are you trying to install?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
terryc
over 11 years ago
7.2 on window 7 using AS7
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alex Weller
Appian Employee
over 11 years ago
Have you configured the security domain (something new for this version that was not in Appian 6)
forum.appian.com/.../Configuring_Relational_Databases
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
terryc
over 11 years ago
I did not, but I am using integrated security with Window (SQL Server on Windows
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eric
Appian Employee
over 11 years ago
Terry, is that custom.properties excerpt from the <appian_install>/runtime_ear/suite.ear/conf directory or the <build>/ear/suite.ear/conf directory? Is the conf.data.datasources.primary.jndiname token actually commented out in the build file?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
terryc
over 11 years ago
Also, the error is javax.naming.NameNotFoundException not unable to connect or loging failed. It seems is a jndi resolution issue
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
terryc
over 11 years ago
No, it is not commented out. The error fronm JBoss actually has the correct jndi name. Just jboss can't find it
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>