We have set up Content Server in the previous chapter and are all set to create our first Docbase. Once the Docbase is ready, we can create our custom DocApps in the Docbase and play around with our custom‑defined objects.
First things first—let's come up with a good (and of course rational) name for your Docbase before we jump ahead. In this book, dev_doc
is the name we have chosen. Our custom Docbase will be referred to by this name throughout this book.
As with almost all commercial software, there are a handful of prerequisites for setting up a Docbase. There is no harm repeating that one should always consult the concerned Release Notes in their entirety to avoid any unforeseen hiccups during the installation process.
Figure 6.2 lists some points to be borne in mind before commencing with Docbase creation:
Entity |
Comments |
---|---|
Content Server |
Should be setup correctly before creating a Docbase. |
Windows Regional Settings |
Need to be set to specify a four-digit date format. |
Docbase Name |
Limitations: Maximum length is 32 characters. Can consist of letters, numbers, and underscores. The first character should be a letter. Should not contain white spaces or non-alphanumeric characters. Cannot have the name "docu". Must be unique in the case of multiple Docbases on the same Content Server. |
Docbase ID |
Limitations: Must be a number in the range 1 to 16777215. Should not start with zero (0). Must be unique in the case of multiple Docbases on the same Content Server. |
Docbase Owner |
Limitations for installation owner's user name: Consists of numbers, letters, hyphens, and underscores. The first character should be a letter. All characters must be ASCII. Password should consist of numbers, letters, periods, hyphens, and underscores. Must be unique in case of multiple Docbases on the same Content Server. |
ODBC Data Source |
Should be correctly configured in case of SQL Server. |
The created DSN now shows up along with other DSNs in the System DSN tab. Finally click on OK. We have successfully created a DSN for connecting to a SQL Server database.
The following error message might be seen if the domain is unavailable due to connectivity issues or if some changes have been made to the domain the user is a member of:
"Unable to initialize admin dll (OSEnv)"
This example uses the Express Configuration type to create the Docbase.
In this example, the defaults provided by Documentum for Docbase owner name (the name of the specified Docbase) have been chosen. The default database name is in the following format: DM_<Specified Docbase name>_docbase
After the Docbase has been created and if someone has unknowingly changed the password for the Docbase owner (DB owner), then the following error message is seen during Docbase startup:
[DM_SESSION_I_RETRYING_DATABASE_CONNECTION] info: "The following error was encountered trying to get a database connection: STATE=28000, CODE=18456, MSG=[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'dev_doc'.
The following error message is seen during Docbase startup if Docbase was configured on a Content Server with case-insensitive SQL Server:
[DM_SESSION_I_INIT_BEGIN]info: "Initialize Crypto Objects."
[DM_SESSION_E_INIT_FAILURE1]error: "Failure to complete Crypto Objects initialization."
[DM_SERVER_I_START_ID]info: "Docbase dev_doc was not successfully opened.
You can create multiple Docbases on the same Content Server with different names to serve the purpose of a development Docbase and a test Docbase (for example). Also, you can create multiple servers for a single Docbase so that request processing is spread across multiple servers to achieve performance gains. However, a detailed discussion regarding such configuration is beyond the scope of this book.
18.226.200.16