Español Go to Modeler community Go to Bizagi.com
New Topic
Bizagi Community | Bizagi SuiteTopicQuestionInstallation and set up
photo
Alex Eimer shared this question 4 years ago
Report Abuse
Properties
Category Installation and set up
Tags engine, java, jboss
Similar Topics
Answered

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:

  1. [jboss@ca9eeb8becd3 ~]$ sh deploy-sharemobile-jboss.sh
  2. deployin
  3. now in
  4. /opt/jboss/BizagiBPMJEE/BizagiConsoleManagerJEE/bin
  5. callin update project
  6. [BizagiJEEConsole:UPDATEPROJECT]: Project updated successfully.
  7. ------------------------------------------------------------------------
  8. EXECUTION TIME
  9. ------------------------------------------------------------------------
  10. Total time: 00:00:04.544
  11. Finished at: Sun Jan 29 21:43:57 UTC 2017
  12. ------------------------------------------------------------------------
  13. callin predeploy
  14. [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
  15. ------------------------------------------------------------------------
  16. EXECUTION TIME
  17. ------------------------------------------------------------------------
  18. Total time: 00:00:04.868
  19. Finished at: Sun Jan 29 21:44:02 UTC 2017
  20. ------------------------------------------------------------------------
  21. go to ear file
  22. /opt/jboss/bizagi_projectsShareMobile/JEE
  23. copy ear to jboss
  24. total 20
  25. drwxrwxr-x 2 jboss jboss 4096 Jan 24 21:42 .
  26. drwxrwxr-x 1 jboss jboss 4096 Jan 24 21:47 ..
  27. -rw-rw-r-- 6 jboss jboss 9041 Mar 27 2015 README.txt
  28. done

So what am I doing wrong? sudo sh deploy.sh gave me the same output...

Best Regards,

Alex

  1. #!/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/

2 The same question

Comments (10)

photo
1
Juan Zuluaga ● 4 years ago

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

Reply
photo
1
Alex Eimer ● 4 years ago

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:

  1. [jboss@ca9eeb8becd3 ~]$ pwd

    /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

Reply
photo
1
Juan Zuluaga ● 4 years ago

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

Reply
photo
1
Alex Eimer ● 4 years ago

Dear Juan,

as mentioned in the original question I ran the shellscript from the bin folder...

So here is what I do:
I'm in:

  1. /opt/jboss/BizagiBPMJEE/BizagiConsoleManagerJEE/bin

And I call:

  1. [jboss@ca9eeb8becd3 bin]$ sh JEEConsoleManager.sh updateproject -f ../Project_ShareMobile.xml

Everything is fine.
Now I run:

  1. sh JEEConsoleManager.sh predeploy -p Project_ShareMobile

And the following output comes:

  1. [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:03.600
    Finished at: Wed Feb 01 16:03:50 UTC 2017
    ------------------------------------------------------------------------

This command creates the following LOG:

  1. 2017-02-01 16:03:47,385 [main] INFO BizAgi.bpm.injector.AbstractBizagiInjector - <ConsoleInjector> Loading modules for Console
    2017-02-01 16:03:47,421 [main] INFO BizAgi.bpm.injector.AbstractBizagiInjector - <ConsoleInjector> Loading modules for Catalog
    2017-02-01 16:03:47,427 [main] INFO BizAgi.bpm.injector.AbstractBizagiInjector - <ConsoleInjector> Loading modules for saml-configuration
    2017-02-01 16:03:48,835 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Mapping catalog entities...
    2017-02-01 16:03:49,243 [main] INFO org.reflections.Reflections - Reflections took 299 ms to scan 2 urls, producing 3 keys and 62 values
    2017-02-01 16:03:49,296 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CatalogLanguage-->ObjectType: Language
    2017-02-01 16:03:49,296 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: WorkCalendar-->ObjectType: WorkCalendar
    2017-02-01 16:03:49,304 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CustomJob-->ObjectType: JobScheduler
    2017-02-01 16:03:49,304 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: DataTrigger-->ObjectType: DataTrigger
    2017-02-01 16:03:49,304 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ConnectorSystemEnvironment-->ObjectType: InterfaceConnectorSystemEnvironments
    2017-02-01 16:03:49,304 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ShortcutsClassification-->ObjectType: ShortcutsClassification
    2017-02-01 16:03:49,304 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: EntityConstructor-->ObjectType: EntityConstructor
    2017-02-01 16:03:49,305 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Authentication-->ObjectType: Authentication
    2017-02-01 16:03:49,305 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: AssemblyClass-->ObjectType: AssemblyClass
    2017-02-01 16:03:49,305 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: UserPropertyVO-->ObjectType: UserProperty
    2017-02-01 16:03:49,305 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ActionInstance-->ObjectType: InterfaceActionInstance
    2017-02-01 16:03:49,305 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: BusinessConfiguration-->ObjectType: BusinessConfiguration
    2017-02-01 16:03:49,306 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: EntityActions-->ObjectType: EntityAction
    2017-02-01 16:03:49,306 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ECMFolderVO-->ObjectType: ECMFolder
    2017-02-01 16:03:49,306 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CatalogRule-->ObjectType: BR_Rule
    2017-02-01 16:03:49,307 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: UserGroup-->ObjectType: UserGroup
    2017-02-01 16:03:49,307 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: FlowElementCatalog-->ObjectType: FlowElement
    2017-02-01 16:03:49,307 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: MySearch-->ObjectType: MySearch
    2017-02-01 16:03:49,307 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CatalogRuleFamily-->ObjectType: BR_RuleFamily
    2017-02-01 16:03:49,308 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: QueryDefinitionCatalogVO-->ObjectType: QueryForm
    2017-02-01 16:03:49,308 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: StartTimerJob-->ObjectType: JobScheduler
    2017-02-01 16:03:49,308 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Holidays-->ObjectType: Holidays
    2017-02-01 16:03:49,308 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Layout-->ObjectType: LayoutDefinition
    2017-02-01 16:03:49,308 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Sequence-->ObjectType: Sequence
    2017-02-01 16:03:49,308 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: SystemCatalogEntity-->ObjectType: System
    2017-02-01 16:03:49,309 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: DoNextOnWfCaseVO-->ObjectType: DoNextOnWfCase
    2017-02-01 16:03:49,309 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Connector-->ObjectType: InterfaceConnector
    2017-02-01 16:03:49,309 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CatalogFile-->ObjectType: BR_File
    2017-02-01 16:03:49,309 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CatalogComponentLibrary-->ObjectType: BR_ComponentLibrary
    2017-02-01 16:03:49,309 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Context-->ObjectType: StakeholderSentenceContext
    2017-02-01 16:03:49,310 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Provider-->ObjectType: Provider
    2017-02-01 16:03:49,310 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CaseNumber-->ObjectType: CaseNumber
    2017-02-01 16:03:49,310 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: WebPage-->ObjectType: WebPage
    2017-02-01 16:03:49,310 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CustomizedResultVO-->ObjectType: CustomizedColumn
    2017-02-01 16:03:49,310 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ECMRepositoryVO-->ObjectType: ECMRepository
    2017-02-01 16:03:49,311 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Assembly-->ObjectType: Assembly
    2017-02-01 16:03:49,311 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Hint-->ObjectType: Hint
    2017-02-01 16:03:49,311 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ReplicationJob-->ObjectType: JobScheduler
    2017-02-01 16:03:49,312 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ProcessTrigger-->ObjectType: ProcessTrigger
    2017-02-01 16:03:49,312 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: DefaultFilter-->ObjectType: DefaultFilter
    2017-02-01 16:03:49,312 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: MessageTemplateVO-->ObjectType: MessageTemplate
    2017-02-01 16:03:49,313 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Icon-->ObjectType: Icon
    2017-02-01 16:03:49,313 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Fact-->ObjectType: Fact
    2017-02-01 16:03:49,313 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: UserToStakeholderRelation-->ObjectType: UserToStakeholderRelation
    2017-02-01 16:03:49,313 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: CatalogResource-->ObjectType: Resource
    2017-02-01 16:03:49,314 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Assignation-->ObjectType: Assignation
    2017-02-01 16:03:49,314 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: EnvironmentConfiguration-->ObjectType: EnvironmentConfiguration
    2017-02-01 16:03:49,314 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ProcessShortcuts-->ObjectType: ProcessShortcut
    2017-02-01 16:03:49,315 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ECMContentTypeVO-->ObjectType: ECMContentType
    2017-02-01 16:03:49,315 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: VirtualCollection-->ObjectType: VirtualCollection
    2017-02-01 16:03:49,315 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ConnectorPackage-->ObjectType: InterfaceConnectorPackage
    2017-02-01 16:03:49,315 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: EntityValueVO-->ObjectType: EntityValue
    2017-02-01 16:03:49,316 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: Theme-->ObjectType: Theme
    2017-02-01 16:03:49,325 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: DimensionVO-->ObjectType: Dimension
    2017-02-01 16:03:49,326 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: LDAPConfiguration-->ObjectType: LDAPConfiguration
    2017-02-01 16:03:49,326 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: SystemJob-->ObjectType: JobScheduler
    2017-02-01 16:03:49,326 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: ConnectorSystem-->ObjectType: InterfaceConnectorSystem
    2017-02-01 16:03:49,326 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entity: TaskEvent-->ObjectType: TaskEvent
    2017-02-01 16:03:49,326 [main] INFO BizAgi.bpm.catalog.framework.internals.annotations.CatalogEntityAnalyzerDefault - Catalog entities found: 55
    2017-02-01 16:03:50,655 [main] ERROR BizAgi.bpm.catalog.cql.sql.CqlSqlEngine - Error while retrieving workspace object
    com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'BABIZAGICATALOG'.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1493)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:390)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:340)
    at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:179)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:154)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:283)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
    at BizAgi.bpm.dbaccess.DataConnector.executeQuery(DataConnector.java:149)
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.executeQuery(CqlSqlEngine.java:147)
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.getWorkspace(CqlSqlEngine.java:156)
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.executeSystemLoad(CqlSqlEngine.java:140)
    at BizAgi.bpm.catalog.cql.executor.CqlExecutorDefault.executeSystemLoad(CqlExecutorDefault.java:101)
    at BizAgi.bpm.catalog.cql.CqlFacadeDefault.executeSystemLoad(CqlFacadeDefault.java:79)
    at BizAgi.bpm.catalog.cql.CatalogRepositoryDefault.executeSystemLoad(CatalogRepositoryDefault.java:70)
    at BizAgi.bpm.catalog.framework.internals.CatalogServiceDefault.executeSystemLoad(CatalogServiceDefault.java:192)
    at com.bizagi.console.model.ProjectManagerDelegate.getProject(ProjectManagerDelegate.java:45)
    at com.bizagi.console.controller.AppServerManagerController.init(AppServerManagerController.java:55)
    at com.bizagi.console.controller.AppServerManagerController.<init>(AppServerManagerController.java:44)
    at com.bizagi.console.view.cmdline.CommandLineManager.initializePreDeployArgs(CommandLineManager.java:124)
    at com.bizagi.console.view.cmdline.CommandLineView.processRequest(CommandLineView.java:56)
    at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:20)
    2017-02-01 16:03:50,669 [main] ERROR BizAgi.bpm.catalog.cql.sql.CqlSqlEngine - Error while retrieving workspace object
    BizAgi.bpm.catalog.cql.exception.CqlEngineException: Error while retrieving workspace object
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.executeQuery(CqlSqlEngine.java:150)
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.getWorkspace(CqlSqlEngine.java:156)
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.executeSystemLoad(CqlSqlEngine.java:140)
    at BizAgi.bpm.catalog.cql.executor.CqlExecutorDefault.executeSystemLoad(CqlExecutorDefault.java:101)
    at BizAgi.bpm.catalog.cql.CqlFacadeDefault.executeSystemLoad(CqlFacadeDefault.java:79)
    at BizAgi.bpm.catalog.cql.CatalogRepositoryDefault.executeSystemLoad(CatalogRepositoryDefault.java:70)
    at BizAgi.bpm.catalog.framework.internals.CatalogServiceDefault.executeSystemLoad(CatalogServiceDefault.java:192)
    at com.bizagi.console.model.ProjectManagerDelegate.getProject(ProjectManagerDelegate.java:45)
    at com.bizagi.console.controller.AppServerManagerController.init(AppServerManagerController.java:55)
    at com.bizagi.console.controller.AppServerManagerController.<init>(AppServerManagerController.java:44)
    at com.bizagi.console.view.cmdline.CommandLineManager.initializePreDeployArgs(CommandLineManager.java:124)
    at com.bizagi.console.view.cmdline.CommandLineView.processRequest(CommandLineView.java:56)
    at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:20)
    2017-02-01 16:03:50,671 [main] ERROR BizAgi.bpm.catalog.framework.internals.CatalogExceptionHandler - Error executing file system load
    BizAgi.bpm.catalog.cql.exception.CqlException: Error while retrieving workspace object
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.getWorkspace(CqlSqlEngine.java:163)
    at BizAgi.bpm.catalog.cql.sql.CqlSqlEngine.executeSystemLoad(CqlSqlEngine.java:140)
    at BizAgi.bpm.catalog.cql.executor.CqlExecutorDefault.executeSystemLoad(CqlExecutorDefault.java:101)
    at BizAgi.bpm.catalog.cql.CqlFacadeDefault.executeSystemLoad(CqlFacadeDefault.java:79)
    at BizAgi.bpm.catalog.cql.CatalogRepositoryDefault.executeSystemLoad(CatalogRepositoryDefault.java:70)
    at BizAgi.bpm.catalog.framework.internals.CatalogServiceDefault.executeSystemLoad(CatalogServiceDefault.java:192)
    at com.bizagi.console.model.ProjectManagerDelegate.getProject(ProjectManagerDelegate.java:45)
    at com.bizagi.console.controller.AppServerManagerController.init(AppServerManagerController.java:55)
    at com.bizagi.console.controller.AppServerManagerController.<init>(AppServerManagerController.java:44)
    at com.bizagi.console.view.cmdline.CommandLineManager.initializePreDeployArgs(CommandLineManager.java:124)
    at com.bizagi.console.view.cmdline.CommandLineView.processRequest(CommandLineView.java:56)
    at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:20)
    2017-02-01 16:03:50,671 [main] ERROR com.bizagi.console.view.cmdline.CommandLineView - 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
    java.lang.RuntimeException: BizAgi.bpm.catalog.framework.api.exceptions.CatalogException: Error executing file system load
    at com.bizagi.console.model.ProjectManagerDelegate.getProject(ProjectManagerDelegate.java:47)
    at com.bizagi.console.controller.AppServerManagerController.init(AppServerManagerController.java:55)
    at com.bizagi.console.controller.AppServerManagerController.<init>(AppServerManagerController.java:44)
    at com.bizagi.console.view.cmdline.CommandLineManager.initializePreDeployArgs(CommandLineManager.java:124)
    at com.bizagi.console.view.cmdline.CommandLineView.processRequest(CommandLineView.java:56)
    at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:20)
    Caused by: BizAgi.bpm.catalog.framework.api.exceptions.CatalogException: Error executing file system load
    at BizAgi.bpm.catalog.framework.internals.CatalogExceptionHandler.logAndBuildCatalogException(CatalogExceptionHandler.java:26)
    at BizAgi.bpm.catalog.framework.internals.CatalogServiceDefault.executeSystemLoad(CatalogServiceDefault.java:194)
    at com.bizagi.console.model.ProjectManagerDelegate.getProject(ProjectManagerDelegate.java:45)
    ... 5 more

It seems, like there is a database-issue?! But I wasn't able to find something to resolve these errors.
I have created an empty database on a MS-SQL-Server with the name "BizagiStaging". I created a User, everything is double checked and correct in the Project-XML:

  1. <project>
    <name>ShareMobile</name>
    <dbProperties>
    <hostName>111.222.333.444</hostName>
    <portNumber>1433</portNumber>
    <userName>bizagi-sa</userName>
    <password>passwd</password>
    <engine>MICROSOFTSQLSERVER</engine>
    <dbName>BizagiStaging</dbName>
    <isRac>false</isRac>
    </dbProperties>
    <serverProperties class="com.bizagi.console.project.JBossProperties">
    <installationPath>/opt/jboss/jboss-eap-6.4</installationPath>
    <type>JBOSS</type>
    </serverProperties>
    <bizagiHome>/opt/jboss/BizagiBPMJEE</bizagiHome>
    <projectHome>/opt/jboss/bizagi_projects_</projectHome>
    </project>

Do you know what I have to do?


Best Regards,
Alex

photo
1
Alex Eimer ● 4 years ago

Hi Juan,

we are in a running project and this server has to run within this week.

So it would be very nice if you could give us a response asap.

Regards,

Alex

photo
1
Juan Zuluaga ● 4 years ago

Dear Alex,

We were analysing this case with our product team. In summary, it fails because there is not information about a Bizagi database in your XML file. In other words, there are not any own project entities.

It is not possible to publish a Bizagi project on an empty database which does not have project entities neither processes information. We recommend to publish it using a development database.

Another point is to make sure to use 1.6 JDK embedded into Bizagi JEE plugin to avoid compatibility problems with JDBC driver.

Regards

photo
photo
1
Alex Eimer ● 4 years ago

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:

  1. [BizagiJEEConsole:PREDEPLOY] ERROR: Bizagi version could not be generated.

    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

Reply
photo
1
Juan Zuluaga ● 4 years ago

Dear Alex,

In order to solve this problem, please follow these steps:

  1. Download our latest version and our latest JEE Plugin from: https://bizagi.sharefile.com/d-sd9dfd1b065b436db
  2. The relative Console path is not correct. It means that you have installed the Plugin on C:/BizagiJEE/jboss-eap-6.4/standalone/configuration/standalone-bizagi.orig and it does not have the Bizagi version according the console message. You should use this path: C:/BizagiJEE/[11_BIZAGI_VERSION]/jboss-eap-6.4 where [11_BIZAGI_VERSION] is the sent version.

At the end, the main problem is that the file is not located inside the JBOSS folder.

Regards

Reply
photo
1
Alex Eimer ● 4 years ago

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

Reply
photo
1
Viktor Buzga ● 3 years ago

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

Reply
Leave a Comment
 
Attach a file