Friday, May 8, 2020
Monday, January 27, 2014
BMT-MDC-0001 Unable to publish
Errorcode BMT-MDC-0001 Unable to publish BMT MDC
The following error is displayed:
BMT-MDC-0001 Unable to publish.
CCL-RCI-0002 The Soap server returned a Soap fault.
The error messages from Application server engine:
CM-REQ-4023 You cannot create an object at the location "/Public Folders/Models".
This field is displayed on the search results webpage seen by customers, and effects search ranking and relevance. An error is displayed in the Publish Wizard in IBM Cognos 8 BI Framework Manager when attempting to publish or re-publish a package.
Reason
The specified publish location cannot be found, due to either of the following conditions:
The specified folder has been renamed or deleted or
The model has been previously published and has cached the previous publish location, which does not exist anymore.
Procedure
1. re-create the folder structure in IBM Cognos Connection and then re-publish the package
or
2. specify a new publish location using the Publish Wizard in Framework Manager.
The following error is displayed:
BMT-MDC-0001 Unable to publish.
CCL-RCI-0002 The Soap server returned a Soap fault.
The error messages from Application server engine:
CM-REQ-4023 You cannot create an object at the location "/Public Folders/Models".
This field is displayed on the search results webpage seen by customers, and effects search ranking and relevance. An error is displayed in the Publish Wizard in IBM Cognos 8 BI Framework Manager when attempting to publish or re-publish a package.
Reason
The specified publish location cannot be found, due to either of the following conditions:
The specified folder has been renamed or deleted or
The model has been previously published and has cached the previous publish location, which does not exist anymore.
Procedure
1. re-create the folder structure in IBM Cognos Connection and then re-publish the package
or
2. specify a new publish location using the Publish Wizard in Framework Manager.
How do you save an IBM Cognos 8 report to the local file system?
Unable to download HTML outputs, as the 'Download' icon is missing under the 'Actions' column within 'View Report Output versions'
Some output formats, such as HTML, are not by default download-able from the 'View Report Output versions' page.
Procedure
1. Edit the system.xml file found in the <c8>\templates\ps directory. Open the file in your favorite editor and search for the following string:
reportFormats
2. Locate format that you want for download using the 'format id' xml tag. For this example, find format id HTML.
3. Change the downloadable="false" to downloadable="true"
4. Save the file and exit the text editor
5. Restart the IBM Cognos 8 service.
6. After restarting the service, navigate to the 'View Report Output Versions' of a report and note that there is now a download HTML icon beside the HTML saved output.
7. Click the Download icon and click the Save button. Specify a drive and filename and click Close
8. In Windows Explorer it should now be possible to open the html file of the saved report
Some output formats, such as HTML, are not by default download-able from the 'View Report Output versions' page.
Procedure
1. Edit the system.xml file found in the <c8>\templates\ps directory. Open the file in your favorite editor and search for the following string:
reportFormats
2. Locate format that you want for download using the 'format id' xml tag. For this example, find format id HTML.
3. Change the downloadable="false" to downloadable="true"
4. Save the file and exit the text editor
5. Restart the IBM Cognos 8 service.
6. After restarting the service, navigate to the 'View Report Output Versions' of a report and note that there is now a download HTML icon beside the HTML saved output.
7. Click the Download icon and click the Save button. Specify a drive and filename and click Close
8. In Windows Explorer it should now be possible to open the html file of the saved report
How to change the dataSource for a Framework Manager model
How do you move a IBM Cognos 8 BI application (framework/published reports) from one environment into another environment when they do not developed against the same databases?
Create a connection to your test database, create the model and then publish a package.
If the test and production databases are identical, and the only difference is the server in which they reside, the only thing to do is edit the data source you created, and since the databases are identical the only thing you have to edit is the server name. If, however, the connection information is not the same for the production database then once again you would have to edit the data source connection and edit the user ID and password, server name, etc... If the schema is different then, in Framework Manager change Data Source. See Steps below in this article.
If you are moving from for example, an acceptance Cognos 8 BI server to a production server, you must do a deployment export from Acceptance and an Deployment Import on production of the same deployment file.
From the menu on the left, select Search and then enter the following string "deployment archive" (no quotes). From the results scroll down to the entry titled 'Export' and select it. This will bring up a page describing the steps to export a deployment archive and then details on what can be done with this file once it has been created.
Steps:
1. When you change Data Source properties, change the following:
'Schema' if necessary. 'Content Manager Data Source'. This is the name of your data source connection in portal Cognos. Do not change the Name property as it is used in the Framework Manager model!
2. Republish the package for the changes to take effect.
Create a connection to your test database, create the model and then publish a package.
If the test and production databases are identical, and the only difference is the server in which they reside, the only thing to do is edit the data source you created, and since the databases are identical the only thing you have to edit is the server name. If, however, the connection information is not the same for the production database then once again you would have to edit the data source connection and edit the user ID and password, server name, etc... If the schema is different then, in Framework Manager change Data Source. See Steps below in this article.
If you are moving from for example, an acceptance Cognos 8 BI server to a production server, you must do a deployment export from Acceptance and an Deployment Import on production of the same deployment file.
From the menu on the left, select Search and then enter the following string "deployment archive" (no quotes). From the results scroll down to the entry titled 'Export' and select it. This will bring up a page describing the steps to export a deployment archive and then details on what can be done with this file once it has been created.
Steps:
1. When you change Data Source properties, change the following:
'Schema' if necessary. 'Content Manager Data Source'. This is the name of your data source connection in portal Cognos. Do not change the Name property as it is used in the Framework Manager model!
2. Republish the package for the changes to take effect.
Install a Cognos FixPack
Installation InstructionsThis Fix Pack can only be installed over an existing installation of Cognos 8 of the same version and component. IBM Cognos 8 BI Server downloads should be installed before IBM Cognos 8 Go! Mobile downloads on the same machine.
Applying Fix Packs
Always keep your Cognos 8 BI environment running at the latest Fix Pack level to ensure problem-free operation as possible. To install a Fix Pack successfully, perform all of the tasks described below.
Note 1: To install a Fix Pack, you must first download and uncompress the Fix Pack.
Note 2: If you already have Cognos 8 BI products installed in the selected installation path, you must also stop any Cognos services.
Note 2: To determine component versions in the Fix Pack before install, you must first download, uncompress and either unpack the tar file to disk or read the table of contents of the tar file. Packaged components are in the "zipfiles" directory. This can be done using a program like Winzip or 7.zip on a Windows system or a combination of the gunzip and tar commands on UNIX as described below.
To install a Fix Pack
1. Check Fix Pack prerequisites
2. Download the correct .tar.gz Fix Pack file which you can download from fixcentral. You can either choose to access the FTP folder directly or you can use a Java applet called Download Director to download the files.
Note: Some browsers may change the downloaded file type from .tar.gz. to a file type not recognized by the operating system. To correct this, change the file type back to .tar.gz or use Download Director to avoid this issue.
3. Uncompress the Fix Pack
Fix Pack installation images on the FTP site are in compressed format. Before you can install a Fix Pack, you must uncompress the Fix Pack installation image in a temporary directory
3.1 Uncompressing Fix Packs (Linux and UNIX)
Copy the Fix Pack to the appropriate UNIX operating system or Linux operating system.
To uncompress a Fix Pack installation image, perform the following steps:
3.1.1 Change to the directory where you have downloaded the Fix Pack installation image .
3.1.2 Use the GNU "gunzip" command to uncompress and the GNU "Tar" command to extract the file.
3.1.3 Enter the following command to uncompress the file:
gunzip filename.tar.gz
tar xvf –
where filename is the fix pack you are installing.
Note: GNU Zip can be obtained from www.gzip.org and GNU tar can be obtained from www.gnu.org/software/tar
3.2 Uncompress Fix Packs (Windows)
To uncompress a Fix Pack installation image, perform the following steps:
3.2.1 Change to the directory where you have downloaded the Fix Pack installation image.
3.2.2 Double click the self-extracting .tar.gz file.
The WinZip Self Extractor window opens.
3.2.3 Select the option "use folder names"
3.2.4 Click Unzip.
All files are unzipped to the specified folder.
4. Install the Fix Pack
4.1 Launch the issetup application found under the folder
For example under Microsoft Windows XP, the issetup application is issetup.exe and the folder is win32.
4.2 Follow the install wizard steps.
The install will update components (as necessary) in the install location indicated.
5. Configure the Fix Pack
5.1 Open Cognos Configuration Manager
5.2 Save the Configuration Manager settings.
5.3 Restart the Cognos server.
6. Test the new Fix Pack
Test the functionallity of the fix pack and see if the problems described in the fix list are working correctly.
Applying Fix Packs
Always keep your Cognos 8 BI environment running at the latest Fix Pack level to ensure problem-free operation as possible. To install a Fix Pack successfully, perform all of the tasks described below.
Note 1: To install a Fix Pack, you must first download and uncompress the Fix Pack.
Note 2: If you already have Cognos 8 BI products installed in the selected installation path, you must also stop any Cognos services.
Note 2: To determine component versions in the Fix Pack before install, you must first download, uncompress and either unpack the tar file to disk or read the table of contents of the tar file. Packaged components are in the "zipfiles" directory. This can be done using a program like Winzip or 7.zip on a Windows system or a combination of the gunzip and tar commands on UNIX as described below.
To install a Fix Pack
1. Check Fix Pack prerequisites
2. Download the correct .tar.gz Fix Pack file which you can download from fixcentral. You can either choose to access the FTP folder directly or you can use a Java applet called Download Director to download the files.
Note: Some browsers may change the downloaded file type from .tar.gz. to a file type not recognized by the operating system. To correct this, change the file type back to .tar.gz or use Download Director to avoid this issue.
3. Uncompress the Fix Pack
Fix Pack installation images on the FTP site are in compressed format. Before you can install a Fix Pack, you must uncompress the Fix Pack installation image in a temporary directory
3.1 Uncompressing Fix Packs (Linux and UNIX)
Copy the Fix Pack to the appropriate UNIX operating system or Linux operating system.
To uncompress a Fix Pack installation image, perform the following steps:
3.1.1 Change to the directory where you have downloaded the Fix Pack installation image .
3.1.2 Use the GNU "gunzip" command to uncompress and the GNU "Tar" command to extract the file.
3.1.3 Enter the following command to uncompress the file:
gunzip filename.tar.gz
tar xvf –
where filename is the fix pack you are installing.
Note: GNU Zip can be obtained from www.gzip.org and GNU tar can be obtained from www.gnu.org/software/tar
3.2 Uncompress Fix Packs (Windows)
To uncompress a Fix Pack installation image, perform the following steps:
3.2.1 Change to the directory where you have downloaded the Fix Pack installation image.
3.2.2 Double click the self-extracting .tar.gz file.
The WinZip Self Extractor window opens.
3.2.3 Select the option "use folder names"
3.2.4 Click Unzip.
All files are unzipped to the specified folder.
4. Install the Fix Pack
4.1 Launch the issetup application found under the
For example under Microsoft Windows XP, the issetup application is issetup.exe and the
4.2 Follow the install wizard steps.
The install will update components (as necessary) in the install location indicated.
5. Configure the Fix Pack
5.1 Open Cognos Configuration Manager
5.2 Save the Configuration Manager settings.
5.3 Restart the Cognos server.
6. Test the new Fix Pack
Test the functionallity of the fix pack and see if the problems described in the fix list are working correctly.
Subscribe to:
Posts (Atom)