Open Service Catalog Manager

Open Service Catalog Manager is an open source application. More details can be found on its homepage.

Contributions

All contributions are welcome - Open Service Catalog Manager uses the Apache 2.0 license and requires the contributor to agree with the OSCM Individual CLA (ICLA). If the contributor submits patches on behalf of a company, then additionally the OSCM Corporate CLA (CCLA) must be agreed. Even if the contributor is included in such CCLA, she/he is still required to agree with the ICLA. To submit the CLAs please:

• download the ICLA.txt and if needed the CCLA.txt
• fill in the required information and sign them
• scan them as pdf files and email them to [email protected]. We will reply to you as soon as possible.

Releases

Newest releases can be found here.

Getting started and building from sources

Please follow the guide from top to bottom, this is the easiest way to avoid errors later on.

Prerequisites

• Installed Java 7u3 or higher.
• PostgreSQL 9.3 database installer.
• GlassFish 3.1.2.2 server installer.
• Eclipse ECJ 4.2.1 library.
• Apache Ivy 2.4.0 library.

Setting up a workspace

1. Download the latest sources for this and documentation repositories.
2. Import the project into your IDE. You should adjust some of the preferences:

• Set the compiler level to the installed version of Java 1.7.
• Set UTF-8 file encoding and Unix line endings.

Setting up the database

1. Install the database using a path without any whitespaces for installation directory. During installation a system-startup service and a database specific user should be created.
2. Update <postgres-root-dir>/data/postgresql.conf properties:

3. Update <postgres-root-dir>/data/pg_hba.conf properties:

host all all 127.0.0.1/32 trust 
host all all 0.0.0.0/0 trust 
host all all <host-ipv6>/128 trust

4. Confirm all changes and restart PostgreSQL service to apply changes.

Setting up the mail server

1. Download and install any mail server.
2. Create any domain and at least one user account in it.

Setting up server

1. Install the GlassFish server following instructions.
2. Check if the Java location is valid in the following configuration files:

<glassfish-root-dir>/glassfish/config/asenv.bat 
<glassfish-root-dir>/glassfish/config/asenv.con 
<glassfish-root-dir>/mq/etc/imqenv.conf

Building the application

1. Update the properties in /oscm-devruntime/javares/local/. You can also look for examples in this directory:

2. Add the Eclipse ECJ and Apache Ivy libraries to Ant runtime in your IDE.
3. Add the following arguments to JVM: -Dhttp.proxyHost=<proxy-host> -Dhttp.proxyPort=8080.
4. Add the following scripts to Ant view in your IDE:

5. Build the source code of the application using All.BUILD target from /oscm-devruntime/javares/devscripts/build-dev-PackageDeploy.xml. The result will be located in /oscm-build/result.
6. Create the database and server resources using STANDALONE.setup target from /oscm-integrationtests-setup/build.xml. It will also deploy all artifacts to the appropriate domains.

Deploying the application

After the environment is set, developers can use the Ant targets to build/redeploy only specific modules. For example, to redeploy the portal Portal.BUILD and then Portal.REDEPLOY should be run one after another.

Deploying eclipse-birt-runtime

OSCM uses eclipse-birt-runtime to generate reports. After OSCM is deployed, it is time for you to download and deploy eclipse-birt-runtime. You can find it under the link. Birt.war is the application you should be interested in. We advise you to get the latest version. When you have deployed the application, you may upload all the reports that we have designed for you. The reports are delivered with every release in oscm-reports.zip. Just unpack the content to a folder on glassfish where the application has been deployed (usually: ${glassfishHome}\glassfish\domains\{domain}\applications\{ecilpse_runtime_folder}).