Open Service Catalog Manager (OSCM) is an open source application with enterprise quality level. It supports a bright spectrum of use cases, from SaaS Marketplaces to Enterprise IaaS Stores. It offers ready-to-use service provisioning adapters for IaaS providers like Microsoft Azure, Amazon Web Services (AWS), VMWare and OpenStack, but is also open for integrating other platforms.
Service Providers can define their services with flexible price models and publish them to an OSCM Marketplaces. The Service Provider can decide on using the OSCM Billing Engine for the service usage cost calculation, or integrate an external one. Customers can subscribe to and use the services.
Find more details on the OSCM homepage.
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:
The latest releases can be found here.
Read here how to setup and get started.
Please follow this guide from top to bottom, this is the easiest way to avoid errors later on.
Basic:
Install sass
and add it to your PATH - for details see sass-lang
If your network requires a proxy to access the internet you need to specify following arguments to JVM running Ant:
-Dhttp.proxyHost=<proxy-host>
-Dhttp.proxyPort=<proxy-port>
-Dhttps.proxyHost=<proxy-host>
-Dhttps.proxyPort=<proxy-port>
Fill the placeholders <proxy-host>
and <proxy-port>
with the respective host and port number where the proxy is provided.
Add the following scripts to Ant view in your IDE: /oscm-devruntime/build-oscmaas.xml
Run targets Build.LIB
, Build.BES
After the build has finished successfully you'll find the deployable artifacts in/oscm-build/result/package
.
You may want to deploy and test your modifications in a running OSCM environment. Simply copy or replace your build artifact into the respective container.
For example:
docker cp /workspace/oscm-build/result/package/oscm-portal/oscm-portal.war oscm-core:/opt/apache-tomee/webapps/