Version 6.7 requires a relational database. We would like to use Oracle.

josd over 11 years ago

Version 6.7 requires a relational database. We would like to use Oracle.

Question 1 : Are there any restrictions in the naming conventions for Oracle users (schema user, functional user) and Tablespaces ? In other words, do we have a free choice in order to follow our own naming conventions ?

Question 2 : Does the functional user requires more than read/write authorisations ? More meaning alter table etc....

Discussion posts and replies are publicly visible

0 Sathya Srinivasan
Appian Employee
over 11 years ago

1. The system requires a DB to connect to. For Primary data source, the system creates a few tables as standard. As long as you dont have tables with same name conflicting in your schema, it should be okay

2. You will be invoking the service as the 'named' user that you configure in your JNDI. This will be used for all DB related calls such as Executing Write to data stores, query rules etc., unless you use Query database node and override by providing your own u/n and p/w to connect to. Frankly, I have never worked on any projects that allow users to override or provide their own custom details to connect to DB. But if you want, there is an option available.

See:-
forum.appian.com/.../Query_Database_Smart_Service

forum.appian.com/.../Configuring_Relational_Databases_for_Process

forum.appian.com/.../Configuring_Data_Capping
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sanjay over 11 years ago

Just want to add that security settings may have to be configured on the Appian Data Store to allow application users to run query rules & write to datastore nodes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel