JOSSO.orgCommunity Documentation

Chapter 2. JOSSO2 Rollout

2.1. Install JOSSO
2.2. The JOSSO2 Layout

JOSSO ships in two different editions: JOSSO Community Edition (CE) and JOSSO Enterprise Edition (EE).

Frequently updated and bursting with the latest features, CE is the same JOSSO SSO (Single Sign On) that has been available for years; offered for free under the business-friendly LGPL open source license.

JOSSO EE is a supported version targeted for enterprise use. Hardened for security and designed to be rock solid stable, EE is offered with a subscription and support package that allows organizations to build their Internet SSO settings on a stable version of the product that is offered over an extended period of time.

Because the release cycle for EE is longer than it is for CE, each enterprise release is supported for 4 years. All the latest bug fixes are backported to your version of JOSSO for the duration of your subscription. Knowing that their JOSSO-powered Identity and Access Management setting is stable and will run bug-free for years to come gives organizations peace of mind, enabling them to build their sites on a proven, stable platform. In addition, JOSSO's professional services team offers training and consulting on the Enterprise Edition to ensure long-term support and stability for our clients.

The first step is to download the JOSSO distribution.

To download the latest JOSSO Community Edition release, go to: http://sourceforge.net/projects/josso/files/

To request a trial version of the JOSSO Enterprise Edition, use this link : http://www.atricore.com/software/trial

Follow the instructions to enable your JOSSO Enterprise Edition installation.

Expand the file into a directory of your choice. This directory will be the JOSSO2 home directory, which we will refer to as JOSSO2_HOME.

Change to the "bin" directory within JOSSO2_HOME, and execute the "atricore" command. This will bootstrap JOSSO2 and the built-in identity appliances, which offer the essential provisioning interfaces upon which the Atricore Console depends. This process can take several minutes depending on the processing capabilities of the host equipment.

All bundles need to be up and running before using the product, so make sure that they all show an initialization state of "Active". Through the command line console, you can monitor the execution status of all the modules that make up the product. The following command can be used to determine that all JOSSO modules are up and running :

            osgi:list | grep Atricore
        

Make sure that all listed bundles are in the "Active" state.

If startup fails, use the log file located within the JOSSO2_HOME/data/logs directory to diagnose the reason for the failure.

From the Atricore Console, you can specify your digital identity architecture at a birds-eye view level, while still retaining the ability to "drill down" on any single component. Atricore Console also makes it possible for you to seamlessly mix and match the building blocks of your Internet SSO setting, realizing both SAML-compliant Identity Provider and Service Provider roles. These can then be connected to any number of identity sources, automatically provisioning SSO capabilities onto the web container or application server of your choice.

Now you're ready to run the Atricore Console. In order to launch it, hit the following URL: http://josso2host:8081/atricore-console and sign in using the default credentials:'admin' as the username and 'admin' as the password.

The directory structure of JOSSO2 is as follows :


            -<JOSSO_HOME>/ - the path to your JOSSO installation.
                |-- appliances
                |-- bin
                |-- data
                |   |-- cache
                |   |-- derby
                |   |-- generated-bundles
                |   |-- log
                |   |-- port
                |   |-- work
                |       │   │-- repository
                |       │   │-- config
                |-- lib
                |-- lock
                |-- system
    
        

The 'appliances' folder contains identity appliances currently managed by JOSSO. The layout of its content follows the one used for Apache Maven repositories.

The 'bin' folder contains start scripts.

The 'data' folder contains files representing persistent application state information, such as the OSGi bundle cache, database files, log files and temporary artifacts produced as a result of transformation procedures.

The 'lib' folder contains the core libraries for the OSGi Microkernel Implementation on top of which JOSSO builds.

The 'lock' folder is used as a support for fail-over settings when more than one JOSSO instance is used.

The 'system' folder contains the libraries that make up the JOSSO distribution. Its layout is based on the Apache Maven repository.