The installation should be done using root or sudoing. Moreover in order to use a specific user/group to owner the instance, I normally create first the user and add it to Wheel, Admin and any group you want, and after:

[root@xxx]# ./cinstall

Your system type is 'Red Hat Enterprise Linux 6 (x64)'.

Enter instance name <ENSEMBLE>: 

Enter a destination directory for the new instance.

Directory: /engine/ensemble

Directory '/engine/ensemble' does not exist.

Do you want to create it <Yes>? 

Select installation type.

    1) Development - Install Ensemble server and all language bindings

    2) Server only - Install Ensemble server

    3) Custom

Setup type <1>? 3

Disk blocks required  = 2792344

Disk blocks available = 15482688

How restrictive do you want the initial Security settings to be?

"Minimal" is the least restrictive, "Locked Down" is the most secure.

    1) Minimal

    2) Normal

    3) Locked Down

Initial Security settings <1>? 2

What user should be the owner of this instance? ensemble

A Cache account will also be created for user ensemble.

Install will create the following Ensemble accounts for you: 

_SYSTEM, Admin, SuperUser, CSPSystem and ensemble. 

Please enter the common password for these accounts: ensemble

Re-enter the password to confirm it: ensemble

What group should be allowed to start and stop

  this instance? ensemble

Do you want to configure additional security options <No>? y

What is the effective group for Ensemble processes <cacheusr>? ensemble

What is the effective user for the Cache SuperServer

  and its jobs <cacheusr>? ensemble

Hope helps

Maybe you can develop a COS script that you can reuse. This script should create the accounts and make some checks.

We have a project where combine this script with a OS level script (using any shell you want) able to execute the COS task in each instance. It's a lot of work to make it but once developed it saves a lot of time. 


The common approach is set the schema category in the Business Service. If you want to capture everything at BS, this is the right approach if you are using only one HL7 Schema (2.5 for example). But if you use several HL7 Schemas then is better to get them separate in order to use different BS (each one with their own schema).

In any case you can use a main entry point (BS) don't set the HL7 category at BS and set it "manually" at Business Process stage. This approach is not the most elegant because all the messages arrives at BP (with map errors, and without the DocType set). Then search or process them is more complicated.

Hope this help

I understand and am clear about the so "wide" of my question :-)

I wonder if there is something not so complex or something "done" to send directly to a web page the results of a WRITE command. This is something common in Ensemble when creating a namespace  or DeepSee Portal when compile or Build a Cube.

Maybe there is a Zen component or sample CSP/Javascript that do that, etc.