6. Installation
OSCM and IaaS Controller installation is ANT based. All installation packages have the same structure and follow the same installation procedure.
See also Deployment View
OSCM uses two databases, one for the data and one for the persistent JMS queues. The databases must be setup if it is a new installation, or brought to the latest schema for successful application deployment. The applications require proper configuration settings in the database, which must be imported in the database before the deployment. The same is valid for IaaS Controller software. It uses only database(s) for data storage, no messaging.
OSCM operates with two domains: one for the fulltext search indexer application and one for the OSCM applications themselves (portal web application and enterprise part). All necessary domain resources (database connection pools, JMS resources, http listeners etc.) should be created and configured, prior to application deployment. The same is valid for the domain where IaaS Controllers are deployed.
The last step in the installation is the application deployment. OSCM has three applications to be deployed: fulltext search indexer (master indexer), web portal application and enterprise application representing the backend for the web portal and the SOAP and REST API, and command line interface. IaaS Controllers come in a packages with two applications: asynchronous provisioning proxy application (APP) and the IaaS controller or adapter application which connects to the actual IaaS system.