exporting meta data from reportnet

[tbtcust]

Would someone please list all the steps needed to export the table and column meta data from reportnet?

Thanks in advance for any help.

 

[MAJLI]

You can use Framework Manager for Exportin Metadata.
the steps are as below:
Create Deployment Folders
Deployment folders are useful to organize your deployment specifications. You can create deployment folders in the Export and Import tabs, and you can also create folders in folders.
To add deployment specifications to a folder, you can copy themfrom their original location and paste them inside the folder. From the New Import or New Export wizards, you can select the folder where to save a deployment specification. You can also start a new import or export from within a specific folder. By default, it will be saved in that folder.
Steps
1. On the portal toolbar, click Deployment.
2. Click the Export or Import tab.
Tip: To delete a deployment folder, select its check box and click the delete button. It must first be empty.
3. Click the new deployment folder button.
Tip: You can also create a deployment folder when you export or import. In the Specify a Name and Description page, click Select another location, and then click New folder.
4. Type a name and, if you want, a description for the folder.
5. If you want to change the location of the folder, click Select another location, and then either click the desired location or click New folder to create another folder. In the Select a location page, click OK.
6. Click Finish.
7. Select the check box next to the new folder, then click the set properties button.
8. Click the General tab.
9. Set the language for the folder.
10. Type in a name, description, and screen tip for the folder.
11. If you want to disable the folder, select the Disable check box.
12. If you have permissions for an Export folder, you can click the Permissions tab, and select the check boxes to grant or deny permissions for the folder.
13. Click OK.

Steps(export)
1. In the source environment, on the portal toolbar, click Deployment.
2. Click the Export tab.
3. Choose whether to use a new or existing deployment specification:
• To use a new deployment specification, on the toolbar, click the new export button. The New Export wizard appears.
• To use an existing deployment specification, in the Actions column, click the update export button for the deployment specification you want. The summary page appears. Proceed to step 15.
4. Type a unique name and, if you want, a description and screen tip for the deployment specification, select the folder where you want to save it, and then click Next.
5. Choose whether to export specific folders and directory content or the entire content store:
• To export specific folders and directory content, click Select public folders and directory content, and then click Next.
• To export the entire content store, click Select the entire content store and select whether to include user account information. Click Next and proceed to step 12.
6. In the Public folders content list, select the packages and folders that you want to export.
7. For each package and folder that you export:
• If you want the package or folder to have a different name in the target environment, or to add multilingual names, click the edit icon , type a new name, and click OK. For information about renaming packages, see Renaming Packages and Folders.
• If you do not want users to access the package or folder and its entries, select the check box in the Disable after import column. This is useful when you want to test the reports before you make them available in the target environment.
8. Under Options, select whether you want to export the report output versions, run history, and schedules and what to do with entries in case of a conflict.
9. Click Next.
10. In the Select the directory content page, select the content and options to export, and then click Next.
11. In the Specify the general options page, select whether to include access permissions and references to external namespaces, and who should own the entries after they are imported in the target environment, and then click Next.
12. In the Specify a deployment archive page, under Deployment archive, do one of the following:
• To create a new deployment archive, click New and then type a name for the deployment archive.
By default, the name of the deployment specification appears.
We recommend that you do not use spaces in the name. If the name of the deployment specification matches the name of an existing deployment archive, the characters _# are added to the end of the name, where # is a number such as 1.
• To replace the contents of an existing deployment archive, click Existing and then click an archive.
13. If you want to secure the archive, under Encryption, click Set the encryption password, type a password, and then click OK.
14. Click Next.
The summary information appears.
Tip: If you want to change information, click Back and follow the instructions.
15. Choose whether to continue the export:
• To continue the export, click Export Now.
ReportNet exports the content you specified to the deployment archive and saves the deployment specification. This may take a few minutes.

When the export request is submitted, the Finish page appears. If you want to view the deployment record, select the View the details of this export after closing the wizard check box. Click Finish.
The View an export deployment record page appears.
• To end the export but save the export deployment specification, click Save Only.
The deployment specification is saved and the Deployment page in Cognos Connection reappears.

 

[tbtcust]

Thanks MAJLI. I'll give this a try and let you know how things turn out.