Documentation update for exporting a project configuration

Technote (troubleshooting)


Problem(Abstract)

There is a correction to the commands used to export a project configuration.

Resolving the problem

You can export the configuration data for a project by using the management console from the command line.

Before you begin

You must know the value of the internal project ID for the project to be exported. Find the value by searching the cci_topology.xml file for type="Project" where property name="contextRoot" and value=project ID as displayed on the Welcome page. The internal project ID is the value where property name="projectID". In the following example excerpt from the cci_topology.xml file, the project ID as displayed on the Welcome page is "myproject" and the internal project ID is "pro00001":

<resource id="project1" state="Complete" type="Project">
<properties>
<property name="projectId" value="pro00001"/>
<property name="contextRoot" value="myproject"/>

About this task

You can export one project configuration at a time.

Ensure that users are not working in Configuration when you perform this task.

The exported project configuration is stored in a JavaScript Object Notation (.json) file in a folder that is named with the project ID. The default location of the folder is stored in the cci_topology.xml file. You can change the default location by updating the cci_topology.xml file. Look for the value where resource id is project-config-ui-1 and property name is configFileDir for the user interface node. For more information about the topology file, see the IBM® Social Media Analytics Installation and Configuration Guide.

Log files for the export process are stored in install_location/cci_tmgmt/BackupRestoreUtility/logs.

Procedure

1. Log in to the user interface node, as the cciusr user.
2. Type the following command:

./cci_cli.sh -u status=complete -r 'post:/projects/internal_project_ID
/exportConfiguration:{"file":"file_name",
"datafetcher":true|false,"hotwords":true|false,"sentiments":true|false,
"typesconcepts":true|false,"mediasets":true|false}'

Where internal_project_ID is the internal project ID that you determined in the About this task section and file_name is the name of the file to export to. You can also specify an absolute or relative path with the file name. If you specify a relative path, the path is relative to the path that is stored in the cci_topology.xml file. Do not insert blanks in the text that occurs between the braces ({}). In the following example the queries, hotwords, types, and concepts for the project with internal project ID pro0000x are exported to /home/cciusr/Project1_backup.json.

./cci_cli.sh -u status=complete -r 'post:/projects/pro0000x/exportConfiguration:
{"file":"/home/cciusr/Project1_backup","datafetcher":true,
"hotwords":true,"sentiments":false,"typesconcepts":true,"mediasets":false}'


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Social Media Analytics

Software version:

1.2

Operating system(s):

Linux

Software edition:

All Editions

Reference #:

1628110

Modified date:

2013-03-11

Translate my page

Machine Translation

Content navigation