Unable to deploy adobe-livecycle-jboss.ear while installing AEM forms 6.2

C_19

07-12-2016

Hi,

 

We are installing AEM forms 6.2 on linux machine.

 

We are using GDS for storing persistent documents(Not Database). While deploying the adobe-livecyle-jboss.ear file we are getting below errors and the adobe generated ear file is not deployed.

 

Logs:

00:16:57,262 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-4) IJ020002: Deployed: file:/e2/jboss/domain/servers/server1/tmp/vfs/deployment/deploymentfd32ef9e6951e882/adobe-dummy-resourceadapter.rar-67595b0496a
839ba/contents/
00:16:57,582 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 79) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "adobe-livecycle-jboss.ear")]) - failure description: {"JBAS014771:
 Services with missing/unavailable dependencies" => [
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.PolicySetManagerBean.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.PolicySetManagerBean]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-wkf-services-ejb.jar\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-dscf.jar\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".LocalUserManagerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".LocalUserManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".PreferencesBean.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".PreferencesBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".AuthenticationManagerBean.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".AuthenticationManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-dsc-bootstrap-ejb.DSCInitializerBeanLocalEJB.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-dsc-bootstrap-ejb.DSCInitializerBeanLocalEJB]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-guides.war\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-XMLFMCallBack.war\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.um-adminui.AdobeIDP2UI_UMUIComponent.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.um-adminui.AdobeIDP2UI_UMUIComponent]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-output-admin-ejb.AdobeIDP2UI_OutputAdmin.ValidatorFactory is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-output-admin-ejb.AdobeIDP2UI_OutputAdmin]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_TaskManagerEJB.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_TaskManagerEJB]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2UI_TrustStoreComponent.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2UI_TrustStore
Component]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".PreferencesBean.ValidatorFactory is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".PreferencesBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".AuthenticationManagerBean.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".AuthenticationManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf-initializer-ejb.adobe_WorkflowInitializerEJB.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf-initializer-ejb.adobe_WorkflowInitializ
erEJB]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_ProcessManagerLocalEJB.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_ProcessManagerLocalEJB]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"edc-server-app.war\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"edc-server-admin.war\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"CoreSystemConfigComponent.jar\".AdobeIDP2UI_CoreSystemConfigComponent.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"CoreSystemConfigComponent.jar\".Adob
eIDP2UI_CoreSystemConfigComponent]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-pg-uicomponent.AdobeIDP2UI_PGUIComponent.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-pg-uicomponent.AdobeIDP2UI_PGUIComponent]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-soap-provider.war\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"dsc.war\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.LicenseManagerBean.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.LicenseManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2UI_TrustStoreComponent.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2UI_Trus
tStoreComponent]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-repository-bindings.jar\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"um-adminui.jar\".deploymentCompleteService]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"HealthMonitorComponent.war\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"HealthMonitorComponent.jar\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.AdminManagerBean.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.AdminManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2UI_TrustStoreComponent.ValidatorFactory is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2
UI_TrustStoreComponent]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"um-scheduler.war\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"um.war\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-output-admin-ejb.AdobeIDP2UI_OutputAdmin.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-output-admin-ejb.AdobeIDP2UI_OutputAdmin]",
    "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adminui.war\".INSTALL is missing [jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-dataservices-integration.war\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.LCContextBean.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.LCContextBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".BootstrapperManagerBean.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".BootstrapperManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-ejb-receiver.Invocation.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-ejb-receiver.Invocation]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.APSDocumentServicesManagerBean.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.APSDocumentServicesManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-ejb-receiver.Invocation.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-ejb-receiver.Invocation]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_ComponentManagerLocalEJB.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_ComponentManagerLocalEJB]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-pg-uicomponent.AdobeIDP2UI_PGUIComponent.HandleDelegate is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-pg-uicomponent.AdobeIDP2UI_PGUIComponent]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".DirectoryServicesManagerBean.Validator is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".DirectoryServicesManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.AdminManagerBean.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.AdminManagerBean]",
    "jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.LCContextBean.ORB is missing [jboss.naming.context.java.comp.adobe-livecycle-jboss.edc-ejb.LCContextBean]",

 

 

Please let me know to get rid of these errors

Accepted Solutions (1)

Accepted Solutions (1)

Khushwant_Singh

12-12-2016

Yes, you still need a DB even if we choose the GDS option. AEM Forms on JEE uses DB to store data related to user management, process management, and other information. You won't be able to login to /adminui and user-related services without a database. 

Regards,
Khushwant Singh

Answers (6)

Answers (6)

C_19

12-12-2016

Thanks for the response @Khushwant.

While installing AEM Forms 6.2.0, We have chosen GDS option for Persistence & Storage. 

We haven't specified database details in domain_<db>.xml because we thought that we don't need any database if we choose GDS option 

Do we still need a DB even if we choose the GDS option?

Khushwant_Singh

09-12-2016

Hi,

Thanks for sharing the logs and other requested information. The JBoss server unable to connect to the database. Kindly run the following command and then deploy the ear file: 

./domain.sh -b <Host IP / Host Name> -c domain_<db>.xml

The domain_<db>.xml file is at JBoss\jboss\domain\configuration.

If the issue still persists, kindly provide the following information

  • Name of the database
  • domain_<db>.xml 

Regards,
Khushwant Singh

C_19

08-12-2016

Thanks for the response @Khushwant.

We are starting the application in Domain mode (not Standalone). We are using Adobe pre-configured JBoss provided with the installer.

Command used:
./domain.sh -b=0.0.0.0 -Djboss.home.dir=/e2/jboss -Djboss.domain.base.dir=/e2/jboss/domain -Djboss.domain.config.dir=/e2/jboss/domain/configuration -c=domain.xml --host-config=host-master.xml -Djboss.node.name=nodeaem3

JBOSS Version is 6.4.5 EAP

Please find the attachment.

Khushwant_Singh

07-12-2016

Hi, 

You might encounter the issue if the JBoss application server is not configured properly or if the application server is not started with a proper command. Kindly share the following information to help you troubleshoot the issue:

  • Are you using Adobe per-configured JBoss provided with AEM Forms installer?
  • Are you using the following command to run JBoss? If not, kindly share the command you are using.
    ./stanalone.sh -b <Host IP / Host Name> -c <configuration_file.xml>
  • Also share JBoss and AEM Forms server logs. JBoss logs are at JBoss<ver>\standalone\log and all the files available at \configurationManager\log\

Regards,
Khushwant Singh