Local server setup

The following table lists the values that can be specified for the Operating System and the corresponding Database value. Unless you change the Operating System, the default for the Local server is AIX. Unless you change the Database, the default for the Local server is Db2.

Content Manager OnDemand supports two types of servers:

The first type of server uses TCP/IP to communicate between the client programs and the server programs. The server programs run on the AIX, IBM® i, Windows, and z/OS operating systems. The databases supported by the server are Db2, Oracle (AIX and Windows platforms only), and Microsoft SQL Server (Windows platforms only). The Content Manager OnDemand objects, such as users, groups, and applications are stored in the database in addition to the index values for the report data that is loaded into the system.

The second type of server is a Local server. The Local server is self-contained (no TCP/IP communication) and is defined using files contained in a directory located on a PC rather than in a database. The files represent the system tables that define the various objects such as users, groups, and applications.

One of the uses of a Local server is to provide the ability to export definitions from a TCP/IP server to a Local server so that the definitions can then be imported to a different TCP/IP server. This is beneficial when a network connection does not exist between two TCP/IP servers. One of the limitations of exporting definitions from a TCP/IP server to a Local server is that the Local server does not support all of the operating-specific or database-specific parameters that are defined when using the administrative client.

When a user logs on to a server, the administrative client determines whether the user has logged on to a Local server or a TCP/IP server. Based on the operating system and database, default settings are established, entry fields are hidden or displayed, and values are added to or removed from selection lists. For definitions that have been exported from a TCP/IP server to a Local server, updating or viewing the definitions might not have the desired results if the Operating System and Database settings of the Local server aren't the same as the TCP/IP server. For example, when an application group and application are exported from a TCP/IP server that is running under AIX to a Local server that has IBM i selected as the operating system, the ACIF indexer that is specified in the application is not supported on the Local server. Therefore, when the application is viewed on the Local server, the Indexer field on the Indexer Information page does not have a value and the ACIF indexer is not listed as a choice of indexers.

To correctly display the operating system and database-specific parameters on a Local server from parameters that have been exported from a TCP/IP server, you must specify the Operating System and the Database when you add the Local server. Then, when a user logs on the Local server from the administrative client, the server resembles and operates like a TCP/IP server for the specified operating system and database. In the example of the application group and application that were exported from the AIX server, the ACIF Indexer is selected when the application is updated or viewed from the Local server.

As another example, a TCP/IP server that is running under AIX uses Oracle as the database. An application group and application are exported from the TCP/IP server to a Local server. To correctly display the database-specific parameters in the application group, the Local server must be added with AIX as the Operating System and Oracle as the Database.