Versions Compared

Old Version 4

changes.mady.by.user Bill Branan

Saved on

compared with

New Version 5

changes.mady.by.user Bill Branan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
titleWindows
  1. Set up OSGi service container
    Code Block
    cd services/servicesadmin
mvn clean -f pom-run.xml pax:provision
cd runner
  2. (Optional) Set the OSGi bundle storage location
    Code Block
    set BUNDLE_HOME=[BUNDLE_HOME]
    1. Wiki Markup
      Where \[BUNDLE_HOME\] is the full path to an empty directory where the osgi container content will be stored
    2. Open the run.bat file in the runner directory in a text editor and replace all instances of "$BUNDLE_HOME" with "%BUNDLE_HOME%"
    3. Note: A directory called "$BUNDLE_HOME" under the runner directory will be used as the default bundle home if one is not specified.
  3. (Optional) Set up logging
    1. Download this the logback.xml file file found here into your bundle home directory.
    2. Open the logback.xml file in a text editor and edit the LOG_FILENAME property to point to a full file path (including file name) for a log file.
    3. Note: One benefit to performing this step will be faster start time for your OSGi container.
  4. Start OSGI service container
    Code Block
    run.bat
    1. The run.bat script will start an OSGi container and commandline interface to it
    2. The container starts with required bundles including the 'services-admin' installed
    3. See discussion below on OSGi container for more details
  5. Once the 'services-admin' is running, check to ensure that it was created properly
    1. In the console where run.bat was executed, an "osgi" prompt should be available. If it is not available, hitting enter should bring it up.
    2. Type "ss" and hit enter. This should list all of the available bundles. This list should include 50 items, all of which are either in the ACTIVE or RESOLVED state.

...