Deployment Manager Known Issues

This Readme document contains late-breaking deployment issues.

Note: The Deployment Manager component is not used with Cognos 8.

Look here for readme information about particular components:

• Installation Known Issues
• Configuration Manager Known Issues
• Data Access (UDA) Known Issues
• Access Manager Known Issues
• Architect Known Issues
• Cognos Application Firewall Known Issues
• Cognos Query Known Issues
• Cognos Scheduler Known Issues
• CognosScript Editor Known Issues
• Impromptu Known Issues
• NoticeCast Known Issues
• PowerPlay Known Issues
• Upfront Known Issues
• Cognos Visualizer Known Issues

The Readme document also contains information about Features No Longer Supported in this release and those that will not be supported in subsequent releases.

To see Readme updates and information about deploying Cognos Enterprise Business Intelligence products, go to the Cognos support site (http://support.cognos.com).

NewsIndex Structure Changed During Deployment Operation

When you redeploy a package from the source environment, any changes that you have made to the NewsIndex structure in the target environment will be overwritten by the structure from the source. This will occur regardless of the merge policy selected, Keep Target or Keep Source.

This situation has no workaround.

347238

Packing Options Not Available when Deploying Multiple Server Groups

If you are using Deployment Manager to pack an installation containing more than one server group per Cognos product, and the server groups are at different release levels, then you may only see those packing options available for the older server group. This occurs because Deployment Manager determines which options to present by communicating with one server group per product. If you have more than one server group, the first group encountered in the Component Specification file is the one whose packing options are displayed. If this is the older server group, only those packing options available when the product was released are displayed.

You likely want to see and use the additional packing options that are available for your newer server group. However, if you use these options, the additional data is packed for the newer server group (which implements the new policies) and is ignored by the older server group.

The ideal option is to upgrade the older server group to the same release level as the newer group, before deploying. This ensures that all options appear, and that consistent data is packed for both groups.

If it is not possible to bring the groups to the same level, you can force Deployment Manager to show the pack options available on the most up-to-date server group for each product. Use the following procedures to have Deployment Manager "ping" all server groups for each product and then communicate with the most recent server group.

Steps for Windows Implementations

1. From the Start menu, select Run and type RegEdit in the value box.
2. Go to: \My_Computer\HKEY_LOCAL_MACHINE\Software\Cognos\cer4\Deployment Manager\CdmConfig
3. Double-click DifferentServerVersions, set its value to 1, and then click OK.
4. Close the registry and restart Deployment Manager.

Steps for Unix Implementations

1. Edit the file: installation_location/cern/cdm/depman.ini.
2. Change the value of DifferentServerVersions to 1.
3. Save and close the file, and then restart Deployment Manager.

nbna

Special Characters in Packlet Location Property for Dependent Components on UNIX

If special characters are used in the Packlet Location property for dependent components on UNIX, the deployment will fail. Special characters include, for example, an ampersand (&), angle brackets (<), and so on.

To avoid this problem, do not use special characters in the Packlet Location property.

347263