Doorgaan naar hoofdcontent

Provisioning: Defining an Application

Introduction


This blog item shows an example on how to define an application that can be used by other Organisations. In this example we have a simple Cordys BOP4 setup. We have only the Default Cluster. In this example the ISV packages are made and it will show how to define the application within CCP. It will show how easy this is within CCP. After this you are able to Provision organisations to use applications within the Cloud.
An introduction to CPP was already given here.

Define the Business Partner
First you will have to define a business partner that developed the ISV. This business partner is needed when defining the Application.


  • Goto System Organization
  • Open Global Business Partners





  • Select +-sign
  • Fill in the details








  • Click Save
Define the Application


Note: A CCP application is NOT a synonym for a ISV package. An application can encompass several packages and a package can be used for the definition of several applications.

  • Goto System Organization
  • Open Global ApplicationsClick +-sign
  • Fill in the Application details:
    Application id: com.ciber.utilityservicesApplication name: CIBER Utility ServicesNote: Within ISV the CIBER Netherlands can be picked

  • Click Save
  • Now the following Tabs are shown at the bottom

The Roles are used to define all the roles that are available for the application.
The X-forms are used for GUIs that are used during provisioning. Here you can add for example an input GUI each time a new Organisation is provisioned. For example to ask for extra attributes.
The BPMs are used during provisioning.

  • Select Roles tab
  • Select the first Role as Role Id

Tip: It is advised to put functional roles in a separate ISV package, maybe in a later blog item i will come back to this.

  • Fill in further details for the Role
  • Click Save
  • Do the same for other Roles
Note: When an application is assigned to an Organisation each Role can be used within that Organisation. You have to be aware of this when defining the application. Sometimes you do not want some Organisations to have a certain Role. In that case it is best to define a separate Application.

After that you have to define on which cluster the application runs.

  • Select Installed on clusters tab
    Click +-sign
  • Select the  Default Cluster
  • Click Save
  • Click Validate (This is important, because then the state of the application becomes In use)
  • Click Back
  • Click Save
Before the application can be used it must be added to a Channel. A Channel in this case is the Global Channel that is defined when installing Provisioning.


Add Application to Default Channel




  • Goto System Organization
  • Open Global Channels

  • Select Collection tab
  • Open Collection










  • Click on +-sign to add an application to this collection
  • Within Application id select the com.ciber.utilityservices application
  • Click Save
Now you can assign Applications to Organisations.

Reacties

Een reactie posten

Populaire posts van deze blog

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h...

Cloud to Cloud Application Integration

A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations. Context The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is als...