Release Notes
Abstract
In a typical installation, the IBM® Content Manager OnDemand and the Microsoft SQL Server reside on the same system. The database used by the Content Manager OnDemand instance is created locally and resides on the local file system.
Although it is not preferred, it is possible to run the Content Manager OnDemand server against a remote SQL Server database. In this case, the database resides on a different machine on which the Microsoft SQL Server is installed.
Content
Let's assume there are two physical Windows machines, the machine with Microsoft SQL Server installed (the SQL Server machine) and the machine with the Content Manager OnDemand Server installed (the Content Manager OnDemand Library Server machine). We will discuss steps to be performed on each machine separately.
Prepare the SQL Server Machine
To install the SQL Server, click setup.exe on the install media. The SQL Server must be installed with Mixed Mode authentication to allow both Windows authentication and SQL Server authentication to be used. For more information about this, refer to this document titled Installing and Configuring Microsoft SQL Server for IBM® Content Manager OnDemand.
After the SQL Server has been installed, start the SQL Server Management Studio and create a database with an upper case name that will be used as the Content Manager OnDemand instance name. Right click Databases and select New Database... Once the database is created, we need to map a user to it and assign a default schema name. This user ID should be the Windows user ID that will be used to create the Content Manager OnDemand instance on the Content Manager OnDemand Library Server machine. If this ID does not exist, go to Security, right click Logins, New Login... to create it. This ID should be set to use the SQL Server authentication. Locate this user ID and double click it to bring up the Login Properties panel. Go to the User Mapping page and select the database we just created. Enter the same user name to the Default Schema field. Click OK to save the changes.
Prepare the Content Manager OnDemand Library Server Machine
The steps for preparing a Content Manager OnDemand Library Server machine might be different depending on what version of Content Manager OnDemand you are running. For example, for Content Manager OnDemand V10.1 with SQL Server 2014 or 2016, we need to install Microsoft SQL Server Management Studio (SSMS). For Content Manager OnDemand V10.5, we need to install the Microsoft ODBC Driver for SQL Server.
The Microsoft ODBC Driver for SQL Server can be downloaded from the following link. It comes with both 32-bit and 64-bit. For Content Manager OnDemand, only the 64-bit installer is needed.
Download ODBC Driver for SQL Server
Steps to Prepare the Content Manager OnDemand V10.1 Library Server Machine
For Content Manager OnDemand V10.1, the SMO support is included in SQL Server Management Studio (SSMS) 17.9.1, which can be downloaded from the following link.
Release notes for SQL Server Management Studio (SSMS)
1. Install Microsoft SQL Server Management Studio 17.9.1 and the Microsoft ODBC Driver for SQL Server.
2. Install Content Manager OnDemand V10.1.0.0. At the end of the install, check to make sure that the Content Manager OnDemand SMO module is registered by issuing the following command:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{ECC6E2B2-9901-4A26-AEF0-085507A375EF}"
If the registration is successful, it should return the following:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{ECC6E2B2-9901-4A26-AEF0-085507A375EF}\a.1
3. Check to make sure a new database under the same name as the new instance being created by the OnDemand Configurator exists on the SQL server machine.
4. Create a new Content Manager OnDemand server instance by using the OnDemand Configurator. On the Database page, Advanced Options for Microsoft SQL Server panel, enter the host name or IP address of the SQL Server machine in the field labeled Microsoft SQL Server Name.
If the SQL Server was not installed with the default instance name, MSSQLSERVER, you must specify the instance name along with the host name or IP address of the SQL Server machine in the format as shown on the Advanced Options for Microsoft SQL Server panel of the OnDemand Configurator. On the Create OnDemand Database page, click the button labeled "Create Local Database Now" to let the OnDemand Configurator create and configure the remote database automatically for you.
If the OnDemand Configurator is successful in creating the database, proceed to step 5.
If the OnDemand Configurator failed to create the remote database automatically, perform the following steps manually.
Open an OnDemand Command Window and type the following command to create the database tables and indexes:
arsdb -I instance_name -ctv
If the entire process is successful, you should see messages like this:
ARS4018I Creating the Microsoft SQL Server instance_name database
...
ARS4026I Creating table schema_name.arsag
ARS4034I Creating index arsag_name_idx
ARS4026I Creating table schema_name.arsag2fol
ARS4034I Creating index arsag2fol_idx
...
You may also see an exception message such as this:
----------
Cannot write property DefaultSchema.This property is not available on SQL Server 7.0.
Microsoft.SqlServer.Management.Smo.UnknownPropertyException
Int32 PropertyNameToIDLookupWithException(System.String, Microsoft.SqlServer.Management.Smo.PropertyAccessPurpose)
----------
The exception is caused by the arsdb command, which is trying to do the database creation and the database already exists. You need the -c option to create the ODBC data source. If the ODBC data source already exists, you can use the -rtv options to create the database tables and indexes without seeing the exception.
Once the database and tables are created, you need to run arssyscr.exe to initialize the system tables. From the same OnDemand Command Window, enter following commands.
arssyscr -I instance_name -a
arssyscr -I instance_name -l
The Content Manager OnDemand instance with the remote SQL Server database is now created.
5. Before the OnDemand LibSrvr ( instance_name) service can be started, its dependent service, MSSQLServer, should be deselected because the SQL Server service is on a different computer. Locate the OnDemand LibSrvr service for the newly created remote SQL server instance and double click it. Single click the MSSQLServer listed under Required Services to deselect it.
Steps to Prepare the Content Manager OnDemand V10.5 Library Server Machine
For Content Manager OnDemand V10.5, the SMO support is not included in SQL Server Management Studio (SSMS) 18. You can install SSMS 18 for your own use.
The Microsoft ODBC Driver for SQL Server can be downloaded from the following link. It comes with both 32-bit and 64-bit. For Content Manager OnDemand, only the 64-bit installer is needed.
Download ODBC Driver for SQL Server
1. Install Microsoft ODBC Driver for SQL Server.
2. Install Content Manager OnDemand V10.5.0.0.
3. Install Content Manager OnDemand V10.5.0.1. At the end of the install, check to make sure the Content Manager OnDemand SMO module is registered by issuing the following command:
If the registration is successful, it should return the following:
3. Check to make sure a new database under the same name as the new instance being created by the OnDemand Configurator exists on the SQL server machine.
4. Create a new Content Manager OnDemand server instance by using the OnDemand Configurator. On the Database page, Advanced Options for Microsoft SQL Server panel, enter the host name or IP address of the SQL Server machine in the field labeled Microsoft SQL Server Name.
If the SQL Server was not installed with the default instance name, MSSQLSERVER, you must specify the instance name along with the host name or IP address of the SQL Server machine in the format as shown on the Advanced Options for Microsoft SQL Server panel of the OnDemand Configurator. On the Create OnDemand Database page, click the button labeled "Create Local Database Now" to let the OnDemand Configurator create and configure the remote database automatically for you.
If the OnDemand Configurator is successful in creating the database, proceed to step 5.
If the OnDemand Configurator failed to create the remote database automatically, perform following steps manually.
Open an OnDemand Command Window and type the following command to create the database tables and indexes:
arsdb -I instance_name -ctv
If the entire process is successful, you should see messages like this:
ARS4018I Creating the Microsoft SQL Server instance_name database
...
ARS4026I Creating table schema_name.arsag
ARS4034I Creating index arsag_name_idx
ARS4026I Creating table schema_name.arsag2fol
ARS4034I Creating index arsag2fol_idx
...
You may also see an exception message such as this:
----------
Cannot write property DefaultSchema.This property is not available on SQL Server 7.0.
Microsoft.SqlServer.Management.Smo.UnknownPropertyException
Int32 PropertyNameToIDLookupWithException(System.String, Microsoft.SqlServer.Management.Smo.PropertyAccessPurpose)
----------
The exception is caused by the arsdb command, which is trying to do the database creation and the database already exists. You need the -c option to create the ODBC data source. If the ODBC data source already exists, you can use the -rtv options to create the database tables and indexes without seeing the exception.
Once the database and tables are created, you need to run arssyscr.exe to initialize the system tables. From the same OnDemand Command Window, enter following commands.
arssyscr -I instance_name -a
arssyscr -I instance_name -l
The Content Manager OnDemand instance with the remote SQL Server database is now created.
5. Before the OnDemand LibSrvr ( instance_name) service can be started, its dependent service, MSSQLServer, should be deselected because the SQL Server service is on a different computer. Locate the OnDemand LibSrvr service for the newly created remote SQL server instance and double click it. Single click the MSSQLServer listed under Required Services to deselect it.
Related Information
Was this topic helpful?
Document Information
Modified date:
07 January 2022
UID
swg27045505