Deployment - CCM


	Overview
	Component Model
	Container Model
	Component Framework
	Packaging & Deployment
	CCM Server
	Developers Forum
	Contact

Unique Features of CCM

Interworking with EJB

For application development in an EJB environment, EJB-CCM Bridge allows an EJB client to communicate with CCM component through an EJB view. The process of implementing EJB-CCM Bridge

More Details

K2 CIDL COMPILER

CIDL is a declarative language for describing the structure and state of component implementations. A CIDL declaration defines behavioral elements, viz. Executors, which indicates the programming artifact (e.g. a Class definition) that supplies the behavior of the Component or Component Home.

More Details

Deployment is a process of installing software components into the Component Server infrastructure. Before deploying a component, it is packaged into an archive file called Deployment Unit archive, along with the deployment descriptors.

A Deployment Unit archive consist of one or more components and each component can have multiple implementations, implementing the same component but characteristics can differ in terms of programming language, platform or even run time behaviour. Each component have their corresponding softpkg descriptor, CORBA component descriptor and property file descriptor. The package as such is a top level descriptor for the deployment unit, which points to corresponding descriptor file for the respective components.

Deployment

K2 provides deployment module that handles automatic deployment of a CORBA® component independent of the platform. K2 allows remote deployment in any of the CCM servers. Remote deployment means a package that is residing locally on the machine running the Deployment tool, is checked and installed in one of the servers, running anywhere else in the Cluster.

General structure of K2 Deployment Descriptors

Component Descriptor

Open Software Description (OSD) is an XML vocabulary used to describe software component and their relationships to other components. The OSD vocabulary is a standard (open) way to describe software components, their version, their underlying structure and their dependency on other component.

The component server uses three descriptors which are created using the OSD vocabulary. The descriptor are softpkg descriptor, CORBA component descriptor and property file descriptor.

Softpkg descriptor

Complex Dependencies:

Software components often require other components to run. OSD provides a way to specify many levels of dependency for Web-bound software components. The DEPENDENCY element of the OSD vocabulary specifies which files a software package needs to run. Dependencies are installed before their parent SOFTPKG component. If a component has multiple layers of dependencies, the components should be arranged in a hierarchical fashion to assure that the deepest nodes will be installed first.

Java Classes and Applets:

OSD files support the inclusion of Java classes and applets in a distribution unit. Specifically, this is done with the JAVA and PACKAGE tags. When described by an OSD file and packaged in a distribution unit, Java class files and applets can be installed. You can save users time and bandwidth by not overwriting or duplicating Java downloads. Downloading Java applets makes your content accessible offline and saves server cycles.

Operating System and Hardware Platforms:

Another way the OSD vocabulary reduces complexity for the user is by delivering only the software implementation the user needs. The OS and PROCESSOR elements are used to specify the operating system and hardware platforms a software component's IMPLEMENTATION requires.

CORBA component descriptor

This Component Property Descriptor contains configuration parameters of the component that are evaluated during deployment time and allow changing the behaviour of a component after development. Points that are expressed in the Component Property Descriptor include:

	Component types, that implement common programming idioms
	Load balancing and fault tolerance settings
	Security predefinitions
	Transaction settings
	Persistent settings and database mappings

Property file Descriptor

The Attribute Descriptor is a customisation mechanism that allows a ready developed component to be reused in different scenarios by initialising the component attributes to particular values. An example for this kind of customisation is for instance a scripting component, whose behaviour is entirely defined by the script the component will be initialised with.

CORBA® is a Registered Trade Mark of Object Management Group,Inc. in USA and other countries