Other Considerations when Connecting ARCHIBUS to your Database

Sybase Connections

When establishing project list entries for Sybase databases, keep in mind that the project connection entries are different for Sybase Runtime projects than for the full Sybase Single-user or Multi-user databases. The Authoring or Multi-User servers use the JDBC driver (as specified by the Sybase engine type entry in afm-config.xml); the Runtime server uses the JDBC-ODBC bridge (as specified by the Sybase-Runtime database engine type entry in afm-config.xml).

To specify the JDBC connections correctly, either use the Smart Client to create the proper Sybase Runtime or Full Sybase project list entry. Alternately, copy the proper HQ-Sybase-Runtime or HQ-Sybase entry in the default afm-projects.xml that ARCHIBUS installs as a prototype.

Sybase Adaptive Server Anywhere Connection Timeout

If you run ARCHIBUS Web Central continually (which most organizations do), you will want it to be able to maintain its database connections indefinitely. However, multi-user Sybase Adaptive Server Anywhere servers disconnect users by default after 240 minutes of inactivity, meaning that you get timeouts if the system has not been used overnight.

Avoid this by adding a "-ti 0" switch to the database service’s startup options. This sets the Client Idle Time to be indefinite.

(This issue does not affect Sybase servers running on the same machine as ARCHIBUS Web Central, since in this configuration Sybase does not apply the timeout to local shared-memory connections.)

Oracle Log In

When logging in to an Oracle database, remember that the user name and password are case-sensitive.

Application-Level Security

Even if you have SQL-level security in place, you may wish to review the application level security in use on your project. ARCHIBUS application level security is very powerful.

Even if you do not use the application-level security for any other purpose, you may wish to consider the following database elements when deploying ARCHIBUS Web Central:

Security on the ARCHIBUS Users table. The Review Group and Edit Group permissions on each field of the ARCHIBUS Users table controls which users can see and alter user information. This feature is key for the My Profile task in ARCHIBUS Web Central, in which you want to grant users the permission to alter only certain values in their own account.
Membership in the SYS-USRMGR group. Members of this group can use the Alter View Wizard. Even with this tool, users cannot gain access to data for which they do not have field-level or record-level application security, but granting this permission deliberately can reduce confusion and keep your hotlists clean.
Typically, sites only assign the Process Navigator processes that include View Definition Wizard to process owners and system managers. Even if a user loads the View Definition Wizard directly via the URL, they must be a member of the SYSTEM MGR group to run it. Sites can change this security group in the Edit Workflow Rules, using the Security Group field.

In particular, you may wish to remove these permissions from the Guest account, or remove or disable the Guest account altogether.