E1 E900 login failure in Testing Environment

Hi, For those have encountered the mentioned issue where user can login to PD production environment but failed in certain environment Eg.  PY

You may check on the server manager console if the related HTML instance with specific port is running ? If not, pls start the instance. Otherwise, pls turn on the E1 root log 's logging level to higher

http://deploymentServer:8999/manage/home

Select the specific HTML instance and click on jdelog.properties logging. From there, at E1log and change it to low level troubleshooting VERBOSE. And duplicate the error.  The detailed log will be saved in E1 LogMMDDYYY.log

In the log, IF it stated :

30 Sep 2014 10:50:56,384 [DEBUG ] - [JDBJ] Bootstrap session user: . 
30 Sep 2014 10:50:56,384 [DEBUG ] - [JDBJ] Bootstrap session environment: PY900. 
30 Sep 2014 10:50:56,384 [DEBUG ] - [JDBJ] Bootstrap session role: . 
30 Sep 2014 10:50:56,384 [DEBUG ] - [JDBJ] Bootstrap session token: null. 

Assuming Tools Release 9.1.x:

For WebSphere, the runtime JAS.INI is located at:

<SM Agent>/SCFHA/targets/<JAS Instance>/config

---

For WebLogic, the runtime JAS.INI is located at:

<Middleware Home>/user_projects/domains/<domain>/servers/<server instance>/stage/<JAS instance>/app/webclient.war/WEB-INF/classes/

A second copy used by Server Manager that is automatically synchronized with the runtime copy when changes are made using the console:

<SM Agent>/SCFHA/targets/<JAS Instance>/config

A third copy is found at

<SM Agent>/SCFHA/targets/<JAS Instance>/config/ipowl_deployment/webclient.ear/app/webclient.war/WEB-INF/classes

that is used as part of the synchronization process.

(This is why it is strongly suggested to use Server Manager to make modifications as it will handle the synchronization among these 3 locations)

The "runtime copies" are the ones actually used by the JAS application when it starts.

Modify the jdbj.ini as below :

[JDBj-BOOTSTRAP SESSION]
user=JDE
password=JDE
role=*ALL
environment=JPY900

where JDE is the password for the userid JDE in EnterpriseOne. 

And Finally restart the html instance.

Hope that helps..