You can configure a type of repository for the
log messages, and then configure properties for the specific repository.
You can also configure more than one repository for log messages.
Before you begin
Before you specify a database as a repository, ensure
that you
Procedure
- On the computer where you installed Content Manager or
the Application Tier Components, start IBM Cognos® Configuration.
- In the Explorer window, under Environment,
click Logging.
- In the Properties window, use the
following table to help set the log server properties.
Table 1. Log server properties
Task |
Action |
Use TCP between IBM Cognos components on a computer
and its local log server
|
Set the Enable TCP property
to True.
UDP provides faster communication
with a lower risk of lost connections than TCP. However, the risk
of losing a local TCP connection is low. TCP is always used for communication
between a local log server and a remote log server.
|
Change the number of threads available to the
local log server
|
Type the value in the Local log
server worker threads property.
Keep the default
value of 10. The range is between 1 and 20.
However, if you
have a high number of log messages, you can allocate more threads
to improve performance.
|
- In the Explorer window, under Environment,
right-click Logging, and click New
resource > Destination.
- In the Name box, type the name of
the repository.
- In the Type list, click the type
of repository and then click OK.
- If the repository is a file, in the Properties window,
type the appropriate values for the mandatory and optional properties.
- If the repository is a remote log server, in the Properties window,
type the appropriate values for the mandatory and optional properties.
If the Internal dispatcher URI of
the repository computer is configured to use SSL, in the Properties window,
set the Enable SSL property to True.
You
must later specify the log messages repository when you configure
the remote log server.
- If the repository is a database, in the Explorer window,
under Logging, specify the type of database
and its properties, as follows:
- Right-click the database name, and click New resource > Database.
- In the Name box, type the name of the repository.
- In the Type list, click the type of database
and then click OK.
- In the Properties window, type the appropriate
values for the mandatory and optional properties.
For
a Microsoft SQL Server
database, you can choose to use a port number, such as 1433, or a
named instance as the value for the Database server with
port number or instance name property. Include the port
number if you use nondefault ports. Include the instance name if there
are multiple instances of Microsoft SQL
Server.
To connect to a named instance,
you must specify the instance name as a JDBC URL property or a data
source property. For example, you can type localhost\instance1.
If no instance name property is specified, a connection to the default
instance is created.
Note that the properties
specified for the named instance, along with the user ID and password,
and database name, are used to create a JDBC URL. Here is an example:
jdbc:JSQLConnect://localhost\\instance1/user=sa/more
properties as required
- Test the connection to the new database. In the Explorer window,
under Environment, right-click Logging and
click Test.
IBM Cognos components connect to
the database. If you configured more than one database for logging
messages, IBM Cognos components test all the databases.
- Repeat steps 5 to 10 for each repository to which you want
the log server to send messages.
- From the File menu, click Save.
- In the Explorer window, click IBM
Cognos services > IBM Cognos.
- From the File menu, click Restart.
If you selected a database as the repository, IBM Cognos components
create the required tables and fields in the database that you created.
Results
If the repository was a remote log server, configure and start
the remote log server. Then restart the IBM Cognos service on the local computer.If
the repository was a database, you can use IBM Cognos components
to run log reports from the database.
You can also set the
logging level, which controls the amount of detail and type of messages
that are sent to a log file or database. For instructions, see the IBM
Cognos Analytics Administration and Security Guide.