Steps provided by Julie Smiley on 2014-11-03:
Since it was a schema import, then it will use the library names that are on the SHARE production server that the schema export came from. So right now your libraries on the share training server are SHARE and SHARE-Testing. You can update the library names to SHARE-Training and SHARE-Sandbox as they were previously using the command ChangeLibraryName (from the admin guide). Just login to the SHARE library on the share-training.cdisc.org server and go to Administration link on top right corner of page.
ChangeLibraryName | Change the name of an existing library. Note that this command does not affect other libraries that may be viewing or interacting with this library. For this reason any dependencies from other libraries (local or remote) such as visible-asset-sources or federated-repositories should be disconnected prior to changing a library name. Remote clients will also need to change connection information once the library name is changed. Asset data is changed asynchronously and changes may still be in progress after the command returns. | N/A |
|
Once you have that done, you will need to update the report links in the UI. From the home screen, go to the Reports section, then [Manage Reports]. Edit each report and change the link (example below for Governance Monitoring Report):
Currently:
https://share.cdisc.org/sm/birt/frameset?__report=reports/GovernanceMonitoring.rptdesign&libraryID=11:5&{library.property.database_schema_name&server_url=https://share.cdisc.org/sm
Change to:
https://share-training.cdisc.org/sm/birt/frameset?__report=reports/GovernanceMonitoring.rptdesign&libraryID=11:5&{library.property.database_schema_name&server_url=https://share-training.cdisc.org/sm
As far as the configuration goes, the only other place that urls are called out are for the messages (email notifications) that use the SHARE logo, which was uploaded to the share.cdisc.org server. I think it is fine for the training server to just reference the logo from the production server, so the above is all you should need to change.
Regards,
Julie
Since it was a schema import, then it will use the library names that are on the SHARE production server that the schema export came from. So right now your libraries on the share training server are SHARE and SHARE-Testing. You can update the library names to SHARE-Training and SHARE-Sandbox as they were previously using the command ChangeLibraryName (from the admin guide). Just login to the SHARE library on the share-training.cdisc.org server and go to Administration link on top right corner of page.
ChangeLibraryName | Change the name of an existing library. Note that this command does not affect other libraries that may be viewing or interacting with this library. For this reason any dependencies from other libraries (local or remote) such as visible-asset-sources or federated-repositories should be disconnected prior to changing a library name. Remote clients will also need to change connection information once the library name is changed. Asset data is changed asynchronously and changes may still be in progress after the command returns. | N/A |
|
Once you have that done, you will need to update the report links in the UI. From the home screen, go to the Reports section, then [Manage Reports]. Edit each report and change the link (example below for Governance Monitoring Report):
Currently:
https://share.cdisc.org/sm/birt/frameset?__report=reports/GovernanceMonitoring.rptdesign&libraryID=11:5&{library.property.database_schema_name&server_url=https://share.cdisc.org/sm
Change to:
https://share-training.cdisc.org/sm/birt/frameset?__report=reports/GovernanceMonitoring.rptdesign&libraryID=11:5&{library.property.database_schema_name&server_url=https://share-training.cdisc.org/sm
As far as the configuration goes, the only other place that urls are called out are for the messages (email notifications) that use the SHARE logo, which was uploaded to the share.cdisc.org server. I think it is fine for the training server to just reference the logo from the production server, so the above is all you should need to change.
Regards,
Julie
Overview
Content Tools