欢迎投稿

今日深度:

teradata DB connection在Jboss中的配置,

teradata DB connection在Jboss中的配置,


To set up the environment for teradata DB connection in Jboss4.0
Please do several actions to set up the environment for connection to teradata DB in Jboss4.0:

1)Put the named: teradata-ds.xml file into folder below:
JbossFolder\server\default\deploy

2)Put the named: TdgssUserConfigFile.xml file into folder below:
JbossFolder\server\default\conf

3)Put the named: terajdbc4.jar file into folder below:
JbossFolder\server\default\lib


teradata-ds.xml 代码如下:
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>TeradataDS</jndi-name>
<connection-url>jdbc:teradata://serverIPAddress/DATABASE=dbName,TMODE=ANSI,CHARSET=UTF8</connection-url>
<driver-class>com.teradata.jdbc.TeraDriver</driver-class>
<user-name>myName</user-name>
<password>myPassword</password>
</local-tx-datasource>
</datasources>



TdgssUserConfigFile.xml代码如下: 我没去弄明白什么意思,不管他,拿来能用就行^_^

<?xml version="1.0" encoding="US-ASCII"?>

<!-- TDGSS User Configuration File -->

<!-- This file consists of five sections:
Header
LegalValues
Algorithms
GlobalQops
Mechanisms
-->

<TdgssConfigFile>

<Header
Version="1"
ConfigFileType="User">
</Header>

<!-- Mechanisms Section: This section puts it all together; what
mechanisms are available and what QOPs each supports. -->

<Mechanisms>

<!-- One entry for each supported mechanism goes here -->


<!-- Teradata Method 1 -->
<!-- This mechanism is required to support clients prior to
TTU 8.0. Previous clients use a different message
format and therefore require a separate mechanism.

It should not have the attribute DefaultMechanism="no"
since DBSV2 6.0 will not offer TD1 to TTU 8.0 clients.
-->
<Mechanism Name="TD1">

<MechanismProperties
AuthenticationSupported="no"
AuthorizationSupported="no"

MechanismEnabled="yes"
MechanismRank="10"

DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"
/>

</Mechanism>


<!-- Teradata Method 2 (uses AES) -->

<Mechanism Name="TD2">

<MechanismProperties
AuthenticationSupported="no"
AuthorizationSupported="no"

MechanismEnabled="yes"
MechanismRank="20"
DefaultMechanism="no"

DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"

VerifyDHKey="no"
DHKeyP="E4BE0A78F54C4A0B17E7E9249A78BCC08868C17281D8463C880937853E73DDC787E41580A8AFE2594D984C9E0814C590790354ECCD1BE8EA85961E5E0974B32EFE178335F061E80189B4BDAA20F67B47"
DHKeyG="0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005"
/>

</Mechanism>


<!-- SSPI: Kerberos Compatability -->
<!-- This mechanism is required to support clients prior to
TTU 8.0. Previous clients use a different message
format and therefore require a separate mechanism.

It should not have the attribute DefaultMechanism="no"
since DBSV2 6.0 will not offer KRB5C to TTU 8.0 clients.
-->
<Mechanism Name="KRB5C">

<MechanismProperties
AuthenticationSupported="yes"
AuthorizationSupported="no"

MechanismEnabled="yes"
MechanismRank="30"

DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"
/>

</Mechanism>


<!-- SSPI: Kerberos -->

<Mechanism Name="KRB5">

<MechanismProperties
AuthenticationSupported="yes"
AuthorizationSupported="no"

MechanismEnabled="yes"
MechanismRank="40"
DefaultMechanism="no"


DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"

/>

</Mechanism>


<!-- SSPI: NTLM Compatability -->
<!-- This mechanism is required to support clients prior to
TTU 8.0. Previous clients use a different message
format and therefore require a separate mechanism.

It should not have the attribute DefaultMechanism="no"
since DBSV2 6.0 will not offer NTLMC to TTU 8.0 clients.
-->

<Mechanism Name="NTLMC">

<MechanismProperties
AuthenticationSupported="yes"
AuthorizationSupported="no"

MechanismEnabled="yes"
MechanismRank="50"

DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"
/>

</Mechanism>


<!-- SSPI: NTLM -->
<Mechanism Name="NTLM">

<MechanismProperties
AuthenticationSupported="yes"
AuthorizationSupported="no"

MechanismEnabled="yes"
MechanismRank="60"
DefaultMechanism="no"


DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"
/>

</Mechanism>

<!-- LDAPv3 -->

<Mechanism Name="ldap">

<MechanismProperties
AuthenticationSupported="yes"
AuthorizationSupported="yes"

MechanismEnabled="yes"
MechanismRank="70"
DefaultMechanism="no"


DelegateCredentials="no"
MutualAuthentication="yes"
ReplayDetection="yes"
OutOfSequenceDetection="yes"
ConfidentialityDesired="yes"
IntegrityDesired="yes"
AnonymousAuthentication="no"
DesiredContextTime=""
DesiredCredentialTime=""
CredentialUsage="0"

VerifyDHKey="no"
DHKeyP="E4BE0A78F54C4A0B17E7E9249A78BCC08868C17281D8463C880937853E73DDC787E41580A8AFE2594D984C9E0814C590790354ECCD1BE8EA85961E5E0974B32EFE178335F061E80189B4BDAA20F67B47"
DHKeyG="0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005"

LdapServerName=""
LdapServerPort="389"
LdapServerRealm=""
LdapSystemFQDN=""
LdapBaseFQDN=""
/>

</Mechanism>

</Mechanisms>

</TdgssConfigFile>



terajdbc4.jar 请参看附件

OVER

www.htsjk.Com true http://www.htsjk.com/teradata/30506.html NewsArticle teradata DB connection在Jboss中的配置, To set up the environment for teradata DB connection in Jboss4.0 Please do several actions to set up the environment for connection to teradata DB in Jboss4.0: 1)Put the named: teradata-ds.xml f...
相关文章
    暂无相关文章
评论暂时关闭