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

  1. The new library name.

 

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

 

 

Annotation:

  1. ChangeLibraryName may take a bit of time to complete. However, based on my experience running it in Firefox, the command didn't return results but it ran successfully.
  2. Using Asset Management, need to search, edit, and then re-submit these Reference Model assets. Otherwise, clicking the diagrams will result in HTTP 500 error:
    1. CDISC Web Diagram^1
    2. ISO 11179 Based Content Model^1

 

 

Email from JSmiley on  

Anthony, a schema backup and restore is for the entire schema, not for just a single library. Both libraries on the production server would be backed up and both libraries on the training server would be overwritten. As such, I recommend either waiting until the team is ready to do the backup/restore, using the training or sandbox library as is, or Akana setting up a dummy server for the pilot (would need to check into this option if we choose it). Please let me know how you would like to proceed. 

  • No labels