Page History

...

1. From the command line, navigate to the command line tools folder in the repository home directory (see repository installation and administration guide. For example

   Code Block
   cd /opt/eaglei/repo/etc

2. Run the globals-migration.sh} script. You will need to know the administrative credentials for the repository. In the following example, we assume the username for the administrative user is {{adminUser and the password is adminPw. We also assume that the url for the repository is http://foo.bar.edu

   Code Block
   bash globals-migration.sh adminUser adminPw http://foo.bar.edu

Verify Commonly Used Resources works

SWEET

To verify that you have configured Commonly Used Resources correctly for SWEET, try to enter a new Instrument. When selecting a Manufacturer, you should see a group of manufacturers under the heading of Commonly Used Resources (see #SWEETenteringdata

\[TODO\] How to migrate existing data to use the globals 

Advanced Topics

\[TODO\] Details about the implementation

\[TODO\] global annotation on type

\[TODO\] Use of the proxy ng

\[TODO\] Global instances are not searchable as a resource themselves

\[TODO\] NB: Tomcat will appear to take a little bit longer to shut down.  This is expected because of the code for the global harvesting.

Troubleshooting

...

image in SWEET - Entering Data.

Search - Institution (OPTIONAL)

If you have installed institution search and you have successfully migrated your data, you will not notice a difference in the resource's instance page. However, when you click through to a Commonly Used Resource, you will notice that the logo is no longer your institution's logo, but the logo for the Commonly Used Resources data repository.

...

1. Wiki Markup
   \[TODO\] expected logs for successful global harvest

...

\[TODO\] expected logs for correct configuration

...