Astra-BackEnd configuration
Just a small memo to remember the order of execution of the bundles for the Astra BackEnd.
This can be used to configure the development environment in Eclipse, to configure the init.xargs file in a release, etc.
Back end properties:
org.osgi.service.http.port=8080 org.osgi.framework.bootdelegation=*
Bundles execution order:
The current bundles and their priorities for an Astra Back-End execution are listed below:
- jsdk-2.2.jar
- cm_all-2.0.0.jar
- comm-linux_all-2.0.0.jar
- commons-logging_all-2.0.0.jar
- http_all-2.0.0.jar
- axis-osgi_all-0.1.0.jar
PersistencyManager-2.0.0.jar (which will appear as PersistencyManager project in Eclipse)
RemoteFrameworkManager-2.0.0.jar (which will appear as RemoteFrameworkManager project in eclipse)
EventsManager-2.0.0.jar (which will appear as EventsManager project in eclipse)
- CommunityManagerAPI-2.0.0.jar (which will appear as CommunityManagerAPI project in Eclipse)
UserManager-2.0.0.jar (which will appear as UserManager project in Eclipse)
CommunityManager-2.0.0.jar (which will appear as CommunityManager project in Eclipse)
AwarenessApplicationManagerBackend-2.0.0.jar (which will appear as AwarenessApplicationManagerBackend project in Eclipse)
TagManagerBackEnd-2.0.0.jar (which will appear as TagManagerBackEnd project in Eclipse)
RepositoryManager-2.0.0.jar (which will appear as RepositoryManager project in Eclipse)
Ex.:
Some things to remember:
When configuring in Eclipse, remember to have different locations in Main->Instance data for each different run configuration: the config files generated can be overwritten sometimes producing strange effects.
The default Start Level (Main->Start Level) in Eclipse is 20. It is necessary to change it if we exceed that start level in our bundles configuration (otherwise they will not be run).
Ex.:
New!: A new release for Astra node and backend has been added to: http://basar.idi.ntnu.no/svn/astra/WP4-tools/persistence/releases/ASTRA-2.0.1852/ . It includes the newest bundles (EventsManager, ApplicationManager, etc.)
Links:
A file with the information about the run configuration can be found at: