This post describes how to migrate OGCE XRegistry to Apache Airavata Registry.
Apache Airavata contains a migration tool that facilitates the migration of XRegistry resouces to Airavata Registry. Following are the steps to be followed for a migration of resources. (If you find any information missing that should be included in this post, please comment on )
1) Build the Airavata trunk .
2) Unzip the apache-airavata-0.3-incubating-SNAPSHOT.zip.
3) Start Airavata Jackrabbit Server by running the shell script in AIRAVATA_HOME/bin directory.
4) Configure the properties file xregistry.properties file. This properties file consists information of XRegistry and Airavata Registry. (This properties file should be placed in the your classpath)
registryURL=https://YOUR_HOST:19443/xregistry?wsdlFollowing is a description of each of the above mentioned properties;
registryURL - URL of the XRegistry instance.5) Go to the AIRAVATA_HOME/bin directory. Execute the xregistry-migrator shell script with your properly configured xregistry.properties file.
ssl.trustedCertsFile=Directory path Cert file used to connect to XRegistry
ssl.hostcertsKeyFile=Host Certificates key file
myproxyServer - URL for MyProxy credential management service
myproxyUser - User name used for MyProxy credential management service
myproxyPass - Password associated with the myproxy username
myproxyLifetime - Lifetime for myproxy certificate.
jcr.url - URL for JCR Registry
jcr.username - User name used to access the JCR Registry
jcr.password - Password associated with the JCR Registry User name
6) Start the Airavata server using the shell script in AIRAVATA_HOME/bin directory.
Browsing the Airavata Registry
7) Viewing the migrated descriptors.
i) Start the XBaya GUI by using the shell script in AIRAVATA_HOME/bin directory.
ii) Click on the Registry Menu and select “Setup Registry” option. Click ok.
iii) Then using the Registry browser you can view the host, service and application descriptors saved in the registry.
8) Now using the saved application services, you can compose scientific workflows.
1) If there are multiple services under the same name (under different namespaces), those will be renamed (appending _NUMBER to the service name) during migration.
2) If there are multiple applications under the same name (under different namespaces), those will be renamed (appending _NUMBER to the application name) during migration.