In this section: |
The ReportCaster Change Management interface provides a way for you to select specific ReportCaster Repository data belonging to specific users and move that data to another ReportCaster environment. The Repository objects you can move are schedules, schedule distribution lists, and library access lists. Typically, you would move data between:
How to: |
The first time you access the ReportCaster Change Management interface, the Change Management Source Properties window opens and displays the target Repository information, and blank fields related to the source Repository information. Youmust provide the source Repository information needed to make the connection between the two Repositories.
Once this connection information is saved, you will always connect to the repository designated in the source fields when you access the Change Management interface. Once in the Change Management interface, you can change the source connection information whenever you want to connect to a different source repository.
Use the following procedure to set or change the connection properties to the source ReportCaster Repository.
The ReportCaster Change Management Source Properties window automatically displays the target Repository information and if previously saved, the source Repository information. The following image is an example of the Source Properties window that opens when using the Change Management interface for the first time from the target environment.
Information about the ReportCaster Repository you are currently logged into (Target URL and Target Class Name) automatically displays in the Source Properties window. Once you save the source Repository information (Source URL, Source Class Name, User ID, and Password) you will enter in this procedure, that will also be displayed whenever you open the Source Properties window.
Note: Currently, the only available release version is 7.6.x.
The connection properties are saved and you can now work in the Change Management interface.
How to: Reference: |
This section describes how to use the ReportCaster Change Management interface to transfer ReportCaster data to another Repository. The interface enables you to move only one type of repository object for one user at a time.
The Change Management Source Properties window displays the information needed to connect to the source ReportCaster Repository. When you access Change Management for the first time, you must set the source Repository properties.
The ReportCaster interface displays a list of users found in the source repository, as well as a series of headings related to the type of Repository object you selected.
The following image shows the Change Management interface when you select Schedules as the Repository Object.
The following image shows the Change Management interface when you select Distribution Lists as the Repository Object.
The following image shows the Change Management interface when you select Access List as the Repository Object.
Note: You can select only one user for each transfer of data.
The right pane displays the related repository objects owned by the selected user. The following image is an example of a list of schedules for a specific user.
Note: Duplicate records cannot exist in the ReportCaster Repository.
A window opens and displays the status and summary of operations on each repository table that was involved in the data transfer. The information includes the operation (insert or update), whether or not the operation was successful, and if it failed, a brief explanation.
This information is saved in a log file (changemgmt.log) on the Distribution Server in ibi\WebFOCUS77\ReportCaster\log. A new log is created each time you click Insert or Update, so the latest log file is time stamped and renamed with a .bak file extension.
This section provides examples of the Change Management log files that indicate:
The following is an example of a log file indicating a successful transfer of records. It provides details for each repository table involved in the transfer.
The following is an example of a log file indicating that a record already exists in the target Repository.
WebFOCUS |