Chiedi agli espertiAzioni sul documento
CMDBuild 1.4 and Shark Installation
Vai al livello superiore
CMDBuild 1.4 and Shark Installation
Lasciato da
Mario
il
19 dicembre 2011 alle 13:33
I have downloaded and installed cmdbuild-1.4.0.2.zip. During the installation I have chosen the example database, so it is populated with existing cards (Basic archives, Purchases, Locations, Assets, Reports) but no workflows like those shown on User Manual (page 34): Trouble Ticketing and Change request. I am guessing that in order to use those workflows I need to install the shark engine and interface, but I am confused on how to proceed:
1) The file cmdbuild-1.4.0.2.zip contained an "extras" directory with a file cmdbuild-shark.zip with 3 jars and a Shark.conf file. Should these files be copied to the cmdbuild WEB-INF directory ? Should Shark.conf be configured ?
2) Is an Enhydra Shark server (or TWE) required or can it be replaced by the file shark-cmdbuild-1.4.0.2.zip available in downloads ? Can these files be installed on the same tomcat instance as cmdbuild or do they require a separate instance ?
Once the installation is complete and the Workfklow Engine configured in Setup what is required to have access to the workflow cards mentioned above (Trouble Ticketing and Change request) ?
Thank you for your help
Best regards
