Cognos ReportNetTM Installation and Configuration Guide

Cognos ReportNetTM Installation and Configuration Guide Cognos ReportNetTM Installation and Configuration Guide

sharepoint.cabq.gov
from sharepoint.cabq.gov More from this publisher
20.07.2014 Views

Chapter 4: Configuring ReportNet Specify the Amount of Resources the ReportNet Service Uses To improve performance in a distributed environment, you can change the amount of resources that the ReportNet service uses by choosing a configuration template. By default, the ReportNet service is configured to use minimal memory resources to optimize startup time. The ReportNet service is available only on the computers where you installed Content Manager and the report server. Steps 1. Start Cognos Configuration. 2. In the Explorer window, under Environment, ReportNet Service, right-click Cognos ReportNet, and click Delete. This deletes the default configuration template for the service. 3. Right-click ReportNet Service, and click New resource, Configuration. 4. Type a name for the service. In Windows, the name you choose is used to register the service. You will see this name in the list of services running on your computer. In UNIX, the name you choose is used as the process identification number (pid). In both Windows and UNIX, if you don’t use the default port number, the port number is appended to the service name. 5. In the Type box, click the configuration template to use: • If you previously changed the default setting and now want to reduce the startup time, memory footprint, and resources used, click Small configuration. • If you want a balance between fast startup time and quick operating speeds, click Medium configuration. • If you want to maximize operating speeds and if performance is more important than fast startup time, and if your computer has more resources, click Large configuration. 6. In the Properties window, edit the properties so that they are appropriate for your environment. 7. From the File menu, click Save. Change Global Settings You change global settings • to customize language support for the user interface • to customize currency support • to customize content locale support • to map the language used in the product user interface • to map content locales • to add fonts to your ReportNet environment By default, ReportNet ensures that all locales, which may come from different sources and in various formats, use a normalized form. That means that all expanded locales conform to a language and regional code setting. Each computer has a default system locale and one user locale per user. The user locales may be different from the default system locale. Customize Language Support to the User Interface Use the Product Languages table to add or remove the user interface language support. For example, if you do not require a German user interface, you can remove the language from the list. Before you can add language support to the user interface, you must use the Cognos Localization Development Kit to translate the strings that appear in the ReportNet user interface. You must also install the language files on all computers in your distributed installation. For more information, contact your Cognos support representative. 54 Cognos ReportNet TM

Chapter 4: Configuring ReportNet Adding languages to the ReportNet environment does not guarantee that your computer has a font that can display Web pages in your preferred languages. Ensure that you install the appropriate language packs to support the character sets you use. If you change the user interface language of the product, data is not affected. Steps 1. On the computer where you installed Content Manager, start Cognos Configuration. 2. From the Action menu, click Edit Global Configuration. 3. Click the Product Locales tab. 4. Click Add. Tip: To remove support, select the check box next to the Supported Locale and then click Remove. 5. In the second column, type the language portion of a locale. 6. Repeat steps 3 to 5 for other language support that you want to add. 7. Click OK. 8. From the File menu click Save. Customize Currency Support If you require additional currencies or want to remove some from the user interface, you can update the list of supported currencies in the Currencies table. By default ReportNet shows only a subset of supported currencies in the user interface. Currencies are identified by their ISO 4217 currency code. The complete list of supported currencies that can be added are listed in the i18n_res.xml file in the crn_location/bin/ directory. If you add a currency code that is not supported by Cognos, you must manually add it to the i18n_res.xml file in the crn_location/bin/ directory. Copy this file to each ReportNet computer in your installation. Adding currencies to the ReportNet environment does not guarantee that your computer has a font with the required characters to display the currency. Ensure that you install the appropriate language packs to the support currency symbols you use. For example, to display the Indian currency symbol (rupee) correctly, you must run a Japanese operating system or install a Japanese language. Steps 1. On the computer where you installed Content Manager, start Cognos Configuration. 2. From the Action menu, click Edit Global Configuration. 3. Click the Currencies tab. 4. Click Add. Tip: To remove support, select the check box next to the supported item and then click Remove. 5. In the second column, type an appropriate value. The value you add must comply with ISO 4217 codes for the representation of currencies and formats. Usually the value you add is a three-letter alphabetic code. The first two characters are letters representing the ISO 3166 country code for the country the currency is from. The additional letter represents the first letter of the currency. 6. Repeat steps 3 to 5 for other types of support that you want to add. 7. From the File menu, click Save. Customize Content Locale Support To ensure users see reports, data or metadata in their preferred language, or specific to their region, you can add partial locales (language) or complete locales (language-region) to the Content Locales table. This way, if content is available in different languages, or in different locales, it is rendered to users based on their user locale. If a locale is not required, you can remove it from the list. Installation and Configuration Guide 55

Chapter 4: Configuring ReportNet<br />

Specify the Amount of Resources the ReportNet Service Uses<br />

To improve performance in a distributed environment, you can change the amount of resources<br />

that the ReportNet service uses by choosing a configuration template.<br />

By default, the ReportNet service is configured to use minimal memory resources to optimize<br />

startup time.<br />

The ReportNet service is available only on the computers where you installed Content Manager<br />

<strong>and</strong> the report server.<br />

Steps<br />

1. Start <strong>Cognos</strong> <strong>Configuration</strong>.<br />

2. In the Explorer window, under Environment, ReportNet Service, right-click <strong>Cognos</strong><br />

ReportNet, <strong>and</strong> click Delete.<br />

This deletes the default configuration template for the service.<br />

3. Right-click ReportNet Service, <strong>and</strong> click New resource, <strong>Configuration</strong>.<br />

4. Type a name for the service.<br />

In Windows, the name you choose is used to register the service. You will see this name in<br />

the list of services running on your computer. In UNIX, the name you choose is used as the<br />

process identification number (pid). In both Windows <strong>and</strong> UNIX, if you don’t use the default<br />

port number, the port number is appended to the service name.<br />

5. In the Type box, click the configuration template to use:<br />

• If you previously changed the default setting <strong>and</strong> now want to reduce the startup time,<br />

memory footprint, <strong>and</strong> resources used, click Small configuration.<br />

• If you want a balance between fast startup time <strong>and</strong> quick operating speeds, click<br />

Medium configuration.<br />

• If you want to maximize operating speeds <strong>and</strong> if performance is more important than<br />

fast startup time, <strong>and</strong> if your computer has more resources, click Large configuration.<br />

6. In the Properties window, edit the properties so that they are appropriate for your<br />

environment.<br />

7. From the File menu, click Save.<br />

Change Global Settings<br />

You change global settings<br />

• to customize language support for the user interface<br />

• to customize currency support<br />

• to customize content locale support<br />

• to map the language used in the product user interface<br />

• to map content locales<br />

• to add fonts to your ReportNet environment<br />

By default, ReportNet ensures that all locales, which may come from different sources <strong>and</strong> in<br />

various formats, use a normalized form. That means that all exp<strong>and</strong>ed locales conform to a<br />

language <strong>and</strong> regional code setting.<br />

Each computer has a default system locale <strong>and</strong> one user locale per user. The user locales may<br />

be different from the default system locale.<br />

Customize Language Support to the User Interface<br />

Use the Product Languages table to add or remove the user interface language support. For<br />

example, if you do not require a German user interface, you can remove the language from the<br />

list.<br />

Before you can add language support to the user interface, you must use the <strong>Cognos</strong><br />

Localization Development Kit to translate the strings that appear in the ReportNet user interface.<br />

You must also install the language files on all computers in your distributed installation. For more<br />

information, contact your <strong>Cognos</strong> support representative.<br />

54 <strong>Cognos</strong> ReportNet TM

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!