CMDBuild Forum

Shark Workflow

Old Versions
#1

Is there anybody that made it work in CMDBuild 1.0 succesfully?

#2

The Shark instance that is provided with the latest release is working but needs some configuration.

We are writing a short guide on how to configure Shark for CMDBuild.

 

Regards

 

#3
** A short how-to to Shark installation **

 

 

1. Copy the shark folder in the webapps folder of a Tomcat instance different from the one that is running CMDBuild.

Configure shark/conf/Shark.conf changing the following line

     DatabaseManager.ConfigurationDir=${shark_webapp}/conf/dods

where ${shark_webapp} is the shark folder you've just copied.

Change
CMDBuild.WS.ExtSync.EndPoint=http://${serverip}:${serverport}/${cmdbuild_webapp}/services/soap/ExternalSync
CMDBuild.WS.EndPoint=http://${serverip}:${serverport}/${cmdbuild_webapp}/services/soap/Webservices
CMDBuild.EndPoint=http://${serverip}:${serverport}/${cmdbuild_webapp}/shark/

to refer to CMDBuild's URL

Ex.
${serverip}:${serverport}/${cmdbuild_webapp} could be something like "localhost:8080/cmdbuild/"

 and so we could write

   CMDBuild.WS.ExtSync.EndPoint=http://localhost:8080/cmdbuild/services/soap/ExternalSync
   CMDBuild.WS.EndPoint=http://localhost:8080/cmdbuild/services/soap/Webservices
   CMDBuild.EndPoint=http://localhost:8080/cmdbuild/shark/

In shark/META-INF/context.xml change the name of the database, putting the name of cmdbuild database.

Ex.
   url="jdbc:postgresql://localhost/${cmdbuild}"
   url="jdbc:postgresql://localhost/cmdbuild1"

Restart Shark Tomcat.

Notes: 
    Actually shark uses the same db of CMDBuild, storing its data inside schema "shark".

    If you want to restore an empty schema you can run
    ${cmdbuild_home}/WEB-INF/sql/shark_schema/02_shark_emptydb.sql

    The user of shark in postgres is created by cmdbuild with the following sql
    (${cmdbuild_home}/WEB-INF/sql/shark_schema/01_shark_user.sql)

        CREATE ROLE shark LOGIN
        ENCRYPTED PASSWORD 'md5088dfc423ab6e29229aeed8eea5ad290'
        NOSUPERUSER NOINHERIT NOCREATEDB NOCREATEROLE;
        ALTER ROLE shark SET search_path=pg_default,shark;

        Please note that the last line is absolutely needed when using shark on CMDBuild db.


2. When Shark is up and running, configure cmdbuild workflow inside Administration module or edit cmdbuild/WEB-INF/conf/workflow.conf putting the correct address of the Shark web services.

#is the workflow enabled?
enabled=true

#where is the sharkWebServices shark application
endpoint=http://${serverip}:${serverport}/${cmdbuild_webapp}

Ex.
endpoint=http://localhost:8181/shark

Restart CMDBuild Tomcat.

Now CMDBuild is configured ready to run workflow.

 

#4

Hello there,

I understand that this is a very old post, however i'd like to ask if this information still applies to version 2.1.8 ?

There is a configuration for workflow in CMDBuild UI. Unfortunately it is not clear for novice as me as to

what user credentials should be used there.

Is these user and password for database ? I suppose not. Where do I configure shark user and password ?

 

Are those from ${cmdbuild-shark}/conf/Shark.conf ?

 

org.cmdbuild.ws.url=http://localhost:8080/cmdbuild/

org.cmdbuild.ws.username=shark

org.cmdbuild.ws.password=workflow

 

Or those above ones are for shark to interact with cmdbuild ?

 

Please advise.

 

Previously Tecnoteca wrote:
** A short how-to to Shark installation **

 

 

1. Copy the shark folder in the webapps folder of a Tomcat instance different from the one that is running CMDBuild.

Configure shark/conf/Shark.conf changing the following line

     DatabaseManager.ConfigurationDir=${shark_webapp}/conf/dods

where ${shark_webapp} is the shark folder you've just copied.

Change
CMDBuild.WS.ExtSync.EndPoint=http://${serverip}:${serverport}/${cmdbuild_webapp}/services/soap/ExternalSync
CMDBuild.WS.EndPoint=http://${serverip}:${serverport}/${cmdbuild_webapp}/services/soap/Webservices
CMDBuild.EndPoint=http://${serverip}:${serverport}/${cmdbuild_webapp}/shark/

to refer to CMDBuild's URL

Ex.
${serverip}:${serverport}/${cmdbuild_webapp} could be something like "localhost:8080/cmdbuild/"

 and so we could write

   CMDBuild.WS.ExtSync.EndPoint=http://localhost:8080/cmdbuild/services/soap/ExternalSync
   CMDBuild.WS.EndPoint=http://localhost:8080/cmdbuild/services/soap/Webservices
   CMDBuild.EndPoint=http://localhost:8080/cmdbuild/shark/

In shark/META-INF/context.xml change the name of the database, putting the name of cmdbuild database.

Ex.
   url="jdbc:postgresql://localhost/${cmdbuild}"
   url="jdbc:postgresql://localhost/cmdbuild1"

Restart Shark Tomcat.

Notes: 
    Actually shark uses the same db of CMDBuild, storing its data inside schema "shark".

    If you want to restore an empty schema you can run
    ${cmdbuild_home}/WEB-INF/sql/shark_schema/02_shark_emptydb.sql

    The user of shark in postgres is created by cmdbuild with the following sql
    (${cmdbuild_home}/WEB-INF/sql/shark_schema/01_shark_user.sql)

        CREATE ROLE shark LOGIN
        ENCRYPTED PASSWORD 'md5088dfc423ab6e29229aeed8eea5ad290'
        NOSUPERUSER NOINHERIT NOCREATEDB NOCREATEROLE;
        ALTER ROLE shark SET search_path=pg_default,shark;

        Please note that the last line is absolutely needed when using shark on CMDBuild db.


2. When Shark is up and running, configure cmdbuild workflow inside Administration module or edit cmdbuild/WEB-INF/conf/workflow.conf putting the correct address of the Shark web services.

#is the workflow enabled?
enabled=true

#where is the sharkWebServices shark application
endpoint=http://${serverip}:${serverport}/${cmdbuild_webapp}

Ex.
endpoint=http://localhost:8181/shark

Restart CMDBuild Tomcat.

Now CMDBuild is configured ready to run workflow.

 

 

#5
Hi. Can any one answer to Paul questions? I'm having similar problems.

Thanks, Mateusz