Expand my Community achievements bar.

SOLVED

Generic IDs for production runs - Jboss error for new ID added.

Avatar

Level 2

Hi All,

we are working in AEM 6.3 forms setup where we run production requests through set of generic IDs, now we have change request for changing old existing IDs with new IDs. These IDs are given same permissions as previous ids ie admin access to all the servers , access to all temp folders of the server (adobe, crx, windows) for full control usage, and in jboss windows service changing the logon id.  Now when we try to start Jboss service, it says it started but it is not completely up and running.  No logs files are generated nor unable to process the requests with new ids. Any other pointers to look why only adding new IDs are causing these issues ??

@Mayank_Gandhi 

@Deleted Account @aemforms_forums 

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi,

We are talking AEM Forms JEE, correct?
You have not just added IDs but you seem to have replaced the logon ID of the jboss service. If you cannot see log files then the service user probably has insufficient permissions. You may also have to add some windows policies. Manual is here: https://helpx.adobe.com/pdf/aem-forms/6-3/install-single-server-jboss.pdf Chapter 10 is setting up the service.

View solution in original post

5 Replies

Avatar

Correct answer by
Level 4

Hi,

We are talking AEM Forms JEE, correct?
You have not just added IDs but you seem to have replaced the logon ID of the jboss service. If you cannot see log files then the service user probably has insufficient permissions. You may also have to add some windows policies. Manual is here: https://helpx.adobe.com/pdf/aem-forms/6-3/install-single-server-jboss.pdf Chapter 10 is setting up the service.

Avatar

Level 2

Hi, Thanks for the resoponse.

Yes correct its AEM Forms 6.3 clustered environment for JEE. As of now the ids share all the access required. Will recheck on access and windows policies.

Avatar

Employee Advisor
@abhilashy577678 If its clustered make sure locator are started first(if TCP) before starting JBOSS.

Avatar

Level 2

@Mayank_Gandhi- The Jboss is tried starting from both windows->control panel->adminstrative tools-> services- windows service for jboss and click start (As we want to use generic ID added in logon). The jboss service status is showing started, but no log files. And yes we have 2 locator one in master and another is slave1, we are starting TCP first then starting the jboss. The AEM 6.3 setup is running fine since couple of years now already, just now want to change the generic IDs to run the jboss and process the requests with new ids. The old Id and new Id share all the permissions same. Any other pointers to look ?