OSCM 16.1.1

 What's new?

OpenStack Integration upgraded to Identity API V3.0

The OpenStack integration software now requires access to the OpenStack Identity API (Keystone) v3.0.

Domain Name Configuration Setting

In version 3 of the Keystone API, domains have been introduced. A domain is a collection of users and projects that exist within the OpenStack environment. A new setting is available in the configsettings_controller.properties file located in <install_pack_dir>/databases/ app_db of the OpenStack integration software: DOMAIN_NAME. This setting can be used specifying a domain other than the default Keystone domain. The domain name can also be specified in the technical service definition. If this is the case, it overrides the setting in the properties file.

Tenant ID in Technical Service Definition

For the OpenStack service controller, the configsettings_controller.properties file located in <install_pack_dir>/databases/ app_db now contains the TENANT_ID configuration setting instead of the TENANT_NAME setting. The identifier of the tenant for your organization in OpenStack can now also be specified in the technical service definition. If this is the case, it overrides the setting in the properties file.

 Getting OSCM 16.1.1

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.1

 What's new?

VMware vSphere Integration

OSCM comes with an integration package for VMware vSphere:
oscm-vmware-install-pack.zip. VMware vSphere is a server and infrastructure virtualization
platform that allows for running multiple operating systems and applications on a single server, the
vSphere server. It gives you on-demand access to fully configured virtual machines (VMs) that are
provisioned by cloning VM templates provided in vSphere.
The integration of OSCM and vSphere provides for an Infrastructure as a Service (IaaS) solution
that leverages the features of both products: Through services, which are published on a
marketplace in OSCM, users can request and use VMs on a vSphere server. The usage costs
can be calculated and charged by means of the OSCM billing and payment services.
The vSphere integration package provided with OSCM includes all the components required for
connecting an existing OSCM installation with vSphere.
A new manual, Open Service Catalog Manager VMware vSphere Integration (GlassFish), is available describing how to deploy this package and how to create and use services for vSphere on a OSCM marketplace.

 Getting OSCM 16.1

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.0.6

 What's new?

Restricted Access to Marketplaces

Marketplace owners can now restrict the access to their marketplaces to users of specific
organizations. For this purpose, a new menu option, Manage access, is provided in the
administration portal.
If the access is restricted for a marketplace, the users of the authorized organizations need to
log in to be able to see, subscribe to, and use the services published on the marketplace. New
customers cannot register themselves on the marketplace but need to be registered by a supplier,
broker, reseller, or the platform operator.
When a marketplace is created, it is public and accessible by any anonymous or registered users.
A marketplace with restricted access can at any time be made public again.

REST API for Integrating Process Management Systems

For integrating with external process management systems, OSCM now provides REST
(Representational State Transfer) APIs in addition to the existing SOAP-based APIs:

• Trigger service REST API: allows you to create, retrieve, modify, and delete trigger definitions as well as to approve or reject the corresponding actions. At the moment, only Subscribe to
  service, Modify subscription, and Terminate subscription triggers are supported.
• Notification service REST API: defines the required resources for the implementation of a
  notification service that connects OSCM with the process management system.
  The REST APIs use HTTP as the protocol and JSON for data representation and transfer. Basic
  authentication with a user ID and password must be used.

The REST APIs are described in YAML files, which are located in the RESTapis folder of the
OSCM integration package, oscm-integration-pack.zip. The other APIs of OSCM have been
moved to the SOAPapis or JAVAapis folder of the integration package, the apis folder is no longer available.

Partial Support of SAML Logout

OSCM installed in SAML_SP authentication mode now provides partial support of SAML logout:
When a user logs out of a OSCM marketplace or the administration portal, an invalidate
session request is sent to the single logout service of the IdP system and the session in OSCM
is invalidated. The user is directed to a Web page that depends on settings in the IdP system and
in OSCM, and he can log in again.

Pricing Information When Subscribing to a Service

A new option, Show price model, allows customers to view the applicable charging conditions
and prices on any of the pages displayed when subscribing to a service on a marketplace.

 Getting OSCM 16.0.6

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.0.5

 What's new?

Deactivation of Payment Information

OSCM offers a new configuration setting, HIDE_PAYMENT_INFORMATION. By setting it to true,
operators can hide the dialogs and options for specifying payment types and billing addresses on
the marketplaces and exclude customer payment information from billing and payment preview
reports. This is useful for scenarios, where payment information is not required, for example, in an
enterprise set-up, where costs are captured only for transparency reasons but no payments are
collected at all. Billing runs and payment processing are not affected by the setting.
Be aware that the HIDE_PAYMENT_INFORMATION configuration setting is evaluated only once
when OSCM is installed or updated. The value can no longer be changed after OSCM has
been started, not even with a further update installation. Payment information already stored for
customers before setting the value to true in an update installation is not affected, but can no
longer be accessed on the marketplaces.

Support of Microsoft Edge Browser

Microsoft Edge is now supported as a Web browser by the OSCM user interface.

 Getting OSCM 16.0.5

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.0.4

 What's new?

Search for Subscriptions

Users can now search for subscriptions on a marketplace. The new full-text search is available
under Home > My subscriptions and Home > Account > Subscriptions . A user can search
for subscriptions by one or more terms in the subscription name, reference number, parameters
of type string, or custom attributes. The search returns the subscriptions which match the search
criteria and for which the user has the required privileges. The results are displayed in a table
which allows for paging, sorting, and filtering.

 Getting OSCM 16.0.4

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.0.3

 What's new?

Billing engine plug-in

OSCM can now be integrated with one or more external billing systems.
The connection between OSCM and an external billing system is established by means of a
billing adapter, which needs to be implemented by a developer and registered by the operator.
For each technical service, the responsible technology provider can decide whether the native
billing system of OSCM or one of the integrated external ones is to be used. When using an
external billing system, its price models can be imported and displayed for the marketable services
and subscriptions based on the technical service.
The calculation of the costs for using the services and subscriptions as well as the billing and
payment processing take place in the external billing system.

 Getting OSCM 16.0.3

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.0.2

 What's new?

Visibility of Services

Organization administrators and OU administrators can select the services which are to be visible on the marketplace for the members of an organizational unit. With previous releases of OSCM, all services were available for selection both for organization administrators and OU administrators. Now, the list of services for an OU administrator is limited to the ones made available to his organizational unit or units by the organization administrator.

 Getting OSCM 16.0.2

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.0.0

 OSCM 16.0.0

Next public release of OSCM.

Deliverables

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

• oscm-reports.zip
• oscm-install-pack.zip
• oscm-aws-install-pack.zip
• oscm-app-install-pack.zip
• oscm-openstack-install-pack.zip
• oscm-ror-install-pack.zip
• oscm-integration-pack.zip
• oscm-integration-app-pack.zip
• oscm-integration-psp-pack.zip

Documentation

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.