Can't predeploy Project
Hi there,
I'm trying to install the Biazgi Engine on a Server with JBOSS EAP 6.4 on Linux (based on docker image jboss/base-jdk:7).
Im using a docker Image based in on CentOS 7 and OpenJDK 7.
I downloaded the JBOSS-specific Engine and unzipped it.
The I created the the Project-Config-File under BizagiBPMJEE/BizagiConsoleManagerJEE/Project_YYY.xml.
After that I wrote a short skript (attached) to update and predeploy the Projekt.
However the following output comes:
- [jboss@ca9eeb8becd3 ~]$ sh deploy-sharemobile-jboss.sh
- deployin
- now in
- /opt/jboss/BizagiBPMJEE/BizagiConsoleManagerJEE/bin
- callin update project
- [BizagiJEEConsole:UPDATEPROJECT]: Project updated successfully.
- ------------------------------------------------------------------------
- EXECUTION TIME
- ------------------------------------------------------------------------
- Total time: 00:00:04.544
- Finished at: Sun Jan 29 21:43:57 UTC 2017
- ------------------------------------------------------------------------
- callin predeploy
- [BizagiJEEConsole:predeploy] java.lang.RuntimeException: BizAgi.bpm.catalog.framework.api.exceptions.CatalogException: Error executing file system load: BizAgi.bpm.catalog.framework.api.exceptions.CatalogException: Error executing file system load
- ------------------------------------------------------------------------
- EXECUTION TIME
- ------------------------------------------------------------------------
- Total time: 00:00:04.868
- Finished at: Sun Jan 29 21:44:02 UTC 2017
- ------------------------------------------------------------------------
- go to ear file
- /opt/jboss/bizagi_projectsShareMobile/JEE
- copy ear to jboss
- total 20
- drwxrwxr-x 2 jboss jboss 4096 Jan 24 21:42 .
- drwxrwxr-x 1 jboss jboss 4096 Jan 24 21:47 ..
- -rw-rw-r-- 6 jboss jboss 9041 Mar 27 2015 README.txt
- done
So what am I doing wrong? sudo sh deploy.sh gave me the same output...
Best Regards,
Alex
- #!/bin/bash
echo deployin
cd /opt/jboss/BizagiBPMJEE/BizagiConsoleManagerJEE/bin
echo now in
pwd
echo
echo callin update project
sh JEEConsoleManager.sh updateproject -f ../Project_ShareMobile.xml
echo
echo callin predeploy
sh JEEConsoleManager.sh predeploy -p Project_ShareMobile
echo
echo go to ear file
cd /opt/jboss/bizagi_projectsShareMobile/JEE
pwd
echo copy ear to jboss
# cp dist/BizAgi-ear-JBoss.ear /opt/jboss/jboss-eap-6.4/standalone/deployments/
Dear Alex,
In order to deploy JBOSS correctly, follow this article: http://help.bizagi.com/bpm-suite/en/index.html?jee_jboss_deploy.htm.
In addition, verify that your JBOSS is set up correctly according this article: http://help.bizagi.com/bpm-suite/en/index.html?jee_jboss_config.htm
Regards
Hi Juan,
I have followed these instructions strictly! And I even get the same error.
I tried to run the Console just like it's described in the Documentation.
Then I get the following output:
/opt/jboss
[jboss@ca9eeb8becd3 ~]$ sh BizagiBPMJEE/BizagiConsoleManagerJEE/bin/JEEConsoleManager.sh createproject -f /opt/jboss/BizagiBPMJEE/BizagiConsoleManagerJEE/Project_ShareMobile.xml
Error: Unable to access jarfile ../BizAgiConsoleManager.jar
[jboss@ca9eeb8becd3 ~]$
So your documentation is wrong! It does not work the way it's described there...
Furthermore it would be great if the Console would print out which file exactly could not be accessed or what else the problem is. "Error executing file system load" is not a good Errormessage -.-
Best Regards
PS Please tag this post as to be answered again
Dear Alex,
Analysing your results, you need to execute the .sh script from BizagiBPMJEE/BizagiConsoleManagerJEE/bin/ folder. Inside of JEEConsoleManager.sh file, there is a line: java-jar ../BizAgiConsoleManager.jar, which requires that you need to be in exact path.
To get further information about the problem, you can access to the console.log file usually at C:\BizagiJEE\10.7.0.2327\BizagiConsoleManagerJEE\log\console.log
Regards
Hello @Juan,
thanks for the database tip!
If've came further with doing the following steps:
- Setup a database with SQL Server 12.0.5 (2014 SP1 ?!)
- Run "CreateDatabase" in Bizagis MC folder for that server (set configfile before)
- Run "Export" for my local database from the Bizagi Studio (set configfile before)
- Run "CreateImport" on the servers database (set configfile before)
- Configure the Project-XML to the server ip and all the other paths and stuff
- on Linux you have to end the path with "/", otherwise the whole stuff does not work (against you documentation)
- Run BizagiJEEConsole's updateproject
When I now run predeploy or deploy on the JEEConsole get the error:
Error detail: C:/BizagiJEE/11.0.0.2632/jboss-eap-6.4/standalone/configuration/standalone-bizagi.orig (No such file or directory)
The strange thing is, I have set the installationPath to /opt/jboss/jboss-eap-6.4/, but the (pre)deploy command changes my configfile every time I run it!
Why is that happening?!
How can I (pre)deploy my project?!
Best regards,
Alex
Dear Alex,
In order to solve this problem, please follow these steps:
At the end, the main problem is that the file is not located inside the JBOSS folder.
Regards
Hi Juan,
if you haven't recognized it, we are using a Linux OS (centOS)! So the path is a absolut path in the Unixstyle...
I will try to use the newest Bizagi Engine Version, but I am shure, that I have downloaded the newest version a month ago.
Best regards,
Alex
Hi Alex,
I don't know, whether your problem was solved or not, but I will leave this comment here just in case.
We had a problem very similar to your case, almost the same error message was generated by the predeploy script. The solution was, that we had to "finish" the Advanced deployment, hence create a Bex file from the development environment and apply that to the test database, so that it could create some elements in the database, which was necessary for the predeploy to run without a problem. The development environment's database was created by the Studio, and that inserted a lot of elements, which was necessary for the predeploy script (BizagiInfo database table rows are examples for that).
(In my opinion, these should be part of the "Create database" step using CreateDatabase.exe in the MC, which should have all the information necessary to create the test database completely.)
Hope this helps you if you still have the problem.
Best Regards,
Viktor
Comments have been locked on this page!