The following instructions highlight how to try out Maya. At this time, Maya does not have a formal "release" available however we understand that certain developers may wish to setup Maya to begin experimenting how it could work in their environment. The follow steps are designed to use a local Derby database and include example plugins that have a local update site run to expose the Maya features and plugins as needed. In addition, a set of JUnit tests are used to populate the database including configuring default profiles and scanning standard update sites. Once you experiment with this configuration, you can deviate from these steps including registering additional update sites and potentially switching to use other database technologies.

#* Part of preparation includes running update site sync which can take 10-60 minutes depending on network connection

#* Part of preparation includes running update site sync which can take 10-60 minutes depending on network connection

# Run the Maya Launcher via Bootstrap

# Run the Maya Launcher via Bootstrap

#* Launch the '''Java Bootstrap''' launch config from the Run... menu

#* Launch the '''Java Bootstrap''' launch config from the Run... menu

+

#* When prompted for a user name and password, specify '''user''' / '''pass''' or '''admin''' / '''admin'''

+

+

== Database Maintenance ==

+

+

Once you've created the Maya database, you may want to periodically run the '''Rescan Update Sites''' launch configuration. This will have Maya go out and verify that all of the features exposed on the registered update sites are stored within Maya's meta cache. In addition, for this Derby-based usage of Maya, the database itself will have information including the machine's hostname to be used as the web site for the Maya plugins exposed by the update site. In a full installation these files would be hosted on a stable server, though in this setup, since the hostname of the machine could change, you may need to re-initialize the database if certain configuration changes occur.

Revision as of 17:47, 10 May 2007

Contents

Overview

The following instructions highlight how to try out Maya. At this time, Maya does not have a formal "release" available however we understand that certain developers may wish to setup Maya to begin experimenting how it could work in their environment. The follow steps are designed to use a local Derby database and include example plugins that have a local update site run to expose the Maya features and plugins as needed. In addition, a set of JUnit tests are used to populate the database including configuring default profiles and scanning standard update sites. Once you experiment with this configuration, you can deviate from these steps including registering additional update sites and potentially switching to use other database technologies.

On Windows navigate to the directory where there is folders like bin & lib and some other files and create a zip file just containing those files

Place that in the JRE folder for your os in the org.eclipse.maya.server.example.db plug-ins (Note: the file must be named jre_1.6.0.zip)

Build Update Site for the Maya software

Open the site.xml located in the update_site folder of the org.eclipse.maya.server.example.db project click Build All

Start the Maya Web Server

Run the server using the launch config Maya Server (Win)

Prepare the Maya Database including initial population

Run using the Initialize Maya Database launch config

Part of preparation includes running update site sync which can take 10-60 minutes depending on network connection

Run the Maya Launcher via Bootstrap

Launch the Java Bootstrap launch config from the Run... menu

When prompted for a user name and password, specify user / pass or admin / admin

Database Maintenance

Once you've created the Maya database, you may want to periodically run the Rescan Update Sites launch configuration. This will have Maya go out and verify that all of the features exposed on the registered update sites are stored within Maya's meta cache. In addition, for this Derby-based usage of Maya, the database itself will have information including the machine's hostname to be used as the web site for the Maya plugins exposed by the update site. In a full installation these files would be hosted on a stable server, though in this setup, since the hostname of the machine could change, you may need to re-initialize the database if certain configuration changes occur.