{"id":328,"date":"2017-09-20T18:16:40","date_gmt":"2017-09-20T18:16:40","guid":{"rendered":"https:\/\/max-drake.cc\/?p=328"},"modified":"2020-07-10T20:59:06","modified_gmt":"2020-07-10T20:59:06","slug":"setup-shark-together-workflow-server-openmaint-localhost-win-10-pc-part-2","status":"publish","type":"post","link":"https:\/\/max-drake.cc\/?p=328","title":{"rendered":"How to setup openMAINT on localHost (Win 10 PC) Part 2 with Shark Together Workflow Server for workorders"},"content":{"rendered":"

\"\"On Starting openMAINT you get this error of the image to the left on the opening page.<\/p>\n

It is related to the Shark Server.  This is the Workflow server.<\/p>\n

I actually found that the file for shark.war was in fact corrupted with the openMAINT download 1.1 2.4.3  version. See Image 2 below<\/strong>, this shows that although SHARK is running on tomcat server, it has no Display name, and when loading the shark.war file not much happens.<\/p>\n

Go to the CMD Build website and download the version that relates to your version of openMAINT, in my case it is V 2.4.3 , see image 2 below:<\/p>\n

Get this Zip version HERE.<\/a><\/p>\n

You need to unzip it and rename the cmdbuild-shark-server-2.4.3.war <\/strong>to shark.war <\/strong>and then insert it into the C:\\tomcat\\webapp directory and let it unpack<\/p>\n

NOTE- You need to have removed the current C:\\tomcat\\webapp\\shark\\ directory and its sub directories before doing this.<\/p>\n

Then you need to re-edit the context.xm<\/strong>l file and the shark.conf<\/strong> fill as well as the auth.conf<\/strong> file in the C:\\tomcat\\webapp\\openmaint\\WEB-INF\\conf<\/p>\n

I took a lot of time having difficulties with getting this to run. and noted a few comments on the CMDBuild forum regarding this issue.<\/p>\n

Also, you have to look at CMDBuild Technical Manual page 16. This is from their manual:<\/p>\n

<\/a>Configuration of the interface between CMDBuild and Together Workflow Server<\/em><\/h2>\n

You can configure Together Workflow Server modifying certain configuration files.  If Tomcat was already started, you need to stop it and execute the following operations:<\/em><\/p>\n

1)      Database address<\/em><\/h3>\n

In the file  of  the  shark  webapp  {SHARK}\/META-INF\/context.xml  <\/strong>you  have  to configure the address of the database modifying the following row:<\/em><\/p>\n

url=”jdbc:postgresql:\/\/localhost\/${cmdbuild}”<\/em><\/p>\n

For example, if the database has the default name “cmdbuild<\/strong>” and the postgres server is working on the same computer and uses the standard port, you will have:<\/em><\/p>\n

url=”jdbc:postgresql:\/\/localhost\/cmdbuild<\/strong>“<\/em><\/p>\n

2)      URL and service user<\/em><\/h3>\n

In the file {SHARK}\/conf\/Shark.conf <\/strong>set correctly the following parameters:<\/em><\/p>\n

# CMDBUild connection settings org.cmdbuild.ws.url=http:\/\/localhost:8080\/openmaint<\/strong>\/ <\/em><\/p>\n

org.cmdbuild.ws.username=workflow      (leave this alone)<\/strong>
\n<\/em><\/p>\n

org.cmdbuild.ws.password=changeme    (leave this alone)<\/strong>
\n<\/em><\/p>\n

inserting the url related to CMDBuild, the username and the password of the ServiceUser used by Together Workflow Server to use the CMDbuild services.<\/em><\/p>\n

3)      Setup of ServiceUser for Together Workflow Server<\/em><\/h3>\n

With a text editor, open the file {OPENMAINT}\/WEB-INF\/conf\/auth.conf <\/strong>and uncomment the row (or add it)
\n<\/em><\/p>\n

serviceusers.privileged=workflow<\/em><\/strong><\/p>\n

If necessary, replacing to workflow the value inserted for the parameter org.cmdbuild.ws.username<\/em><\/p>\n

at the previous point.<\/em><\/p>\n

4)      Starting the services<\/em><\/h3>\n

The Shark Tomcat service must already be active when you start operating across the workflows using the CMDBuild user interface.<\/em><\/p>\n

On Windows the path should be expressed with the bar reversed:<\/em><\/p>\n

DatabaseManager.ConfigurationDir=C:\/tomcat\/webapps\/shark\/conf\/dods<\/em><\/p>\n

or double<\/em><\/p>\n

DatabaseManager.ConfigurationDir=C:\\\\tomcat\\\\webapps\\\\shark\\\\conf\\\\dods<\/em><\/p>\n

One way to check the proper functioning of the Shark instance is to refer to the its log file<\/strong>. Before pursuing the configuration, reboot the tomcat instance of CMDBuild.<\/em><\/p>\n

5)      Authorizations<\/em><\/h3>\n

From the Administration Module CMDBuild you have to enter the Setup menu and:<\/em><\/p>\n

    \n
  • enable the workflow (with the appropriate checkbox)<\/em><\/li>\n
  • set the URL to which the Shark service responds<\/em><\/li>\n<\/ul>\n

    6)      Create the user in CMDBuild and grant privileges<\/em><\/h3>\n

    From the Administration Module CMDBuild you have to enter the \u201cUsers and Groups\u201d and:<\/em><\/p>\n

      \n
    • under the heading Users, create a new user with user Name and Password corresponding to the values defined with the parameters cmdbuild.ws.username and org.cmdbuild.ws.password in item 2)<\/em><\/li>\n
    • Add the user just created to a Group with administrative privileges (e.g. SuperUsers or a group with the admin flag enabled)<\/em><\/li>\n<\/ul>\n

      \"\"<\/p>\n

       <\/p>\n

      \"\"<\/p>\n

       <\/p>\n

      So after putting shark.war into the C:\\tomcat\\webapp directory (and deleting the old C:\\tomcat\\webapp\\shark directory)<\/p>\n

      Go to Control panel andc System and put in the new Environmental variable<\/p>\n

      \"\"<\/p>\n

      Then shutdown Tomcat, and edit the following files:<\/p>\n

      shark.conf<\/p>\n

      context.xml<\/p>\n

      auth.conf (in openmaint directory)<\/p>\n

      Also create the directory  C:\\tomcat\\webapp\\shark\\conf\\dods <\/strong>as per the environmental variable.<\/p>\n

      In pgAdmin3 for the Database<\/p>\n

      \"\"<\/p>\n

      Make sure the search paths that are set for the gis schema include shark (see earlier post).<\/p>\n

      Then Restart Tomcat, and go to Browser  http:\/\/localhost:8080\/and go to  and to server , you should see that SHARK now has a display name (unlike with the corrupted shark.war file.<\/p>\n

       <\/p>\n

      \"\"<\/p>\n

      Then go to http:\/\/localhost:8080\/openmaint and start it up.<\/p>\n

      On startup you should still get the flags as per first image of this post.<\/p>\n

      You need to go to Data Management Module to last tab at bottom left, “SETUP”, foe Workflow engine<\/p>\n

      \"\"<\/p>\n

       <\/p>\n

      Then go to Users & Groups, create (if not already created- if created , change password to ‘changeme’) and put it in selected for superuser group.<\/p>\n

      \"\"   Then go back to SETUP tab at bottom, go to SERVER MANAGEMENT and clear cache. Then logout and login, hopefully all will be working.<\/p>\n

       <\/p>\n

      The image below shows how the icons look (not cogs) when it isn’t working, \"\"<\/p>\n

      This one shows the cogs, so the processes are working in the instance below.<\/p>\n

      \"\"<\/p>\n

      \"\"<\/p>\n

      This seems to work on my Localhost setups on my personal computers but I cannot seem to get it to work on the remote server yet, after trying all the steps a couple of times. Shark is now working but there seems to be a barrier somewhere with its connection to the database I think.<\/p>\n

      I have made the shark schema owner shark, and my file edits are the same as what I did on the local servers.<\/p>\n

      So I will need to continue to explore.<\/p>\n

       <\/p>\n

       <\/p>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      On Starting openMAINT you get this error of the image to the left on the opening page. It is related to the Shark Server.  This is the Workflow server. I actually found that the file for shark.war was in fact corrupted with the openMAINT download 1.1 2.4.3  version. See Image 2 below, this shows that […]<\/p>\n","protected":false},"author":1,"featured_media":347,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,9],"tags":[16,112,113,53,54,114],"class_list":["post-328","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-openmaint-assettiger","category-openmaint-setup","tag-amfm-data-management","tag-cafm","tag-cmms","tag-facility-management","tag-facility-operations","tag-iwms"],"featured_image_src":"https:\/\/max-drake.cc\/wp-content\/uploads\/2017\/09\/om85.jpg","featured_image_src_square":"https:\/\/max-drake.cc\/wp-content\/uploads\/2017\/09\/om85.jpg","author_info":{"display_name":"Max Drake","author_link":"https:\/\/max-drake.cc\/?author=1"},"_links":{"self":[{"href":"https:\/\/max-drake.cc\/index.php?rest_route=\/wp\/v2\/posts\/328","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/max-drake.cc\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/max-drake.cc\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/max-drake.cc\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/max-drake.cc\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=328"}],"version-history":[{"count":0,"href":"https:\/\/max-drake.cc\/index.php?rest_route=\/wp\/v2\/posts\/328\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/max-drake.cc\/index.php?rest_route=\/wp\/v2\/media\/347"}],"wp:attachment":[{"href":"https:\/\/max-drake.cc\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/max-drake.cc\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/max-drake.cc\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}