PeopleSoft agent v12.0.2

[Fred Shindle]

Has or is anyone successfully installed and running the newest PeopleSoft agent, v12.0.2?

[Legacy User]

Hi FredS ,

I have them on Windows and Linux. Can I help you with something?

Cheers,
Alexander

[Fred Shindle]

 

Alexander,

 

Thanks for reply and did not post questions until I was sure someone had this version successfully running.

 

Sorry for long winded post, trying to cover pieces.

 

We are making jump from AE v9 to v12, one of the agents we are upgrading in v9 is Peoplesoft.

 

The v12.0.* agent is the first that runs via the jar file (ucxjps84.jar) versus the previous versions using the exe ( ucxjpsx.exe).  I have been configuring the new ini file comparing to working v9 ini file noting differences and changes, I believe I am close.

 

I can start the agent which appears to connect initially and stays active but receive the following messages:

 

U02007018 'DOWNbea.jolt.ServiceException: Invalid Session'

 

U02007010 Error connecting to the Application Server '//appserver:9000' and user '*account*'

 

 

 

PeopleSoft admins confirm service account we are using is as it should be.

 

I suspect this error is related to the 'psjoa.jar' file which I can use successfully for any pre v12 agent, psjoa file is for PeopleTools v8.55.

 

 

 

I also know the service account being used is working, including the domain acct/password.

 

“Classes=” has fully qualified paths.

 

Peoplesoft appserver, JOLT port and other configuration items have been triple checked.

 

I have also pointed to and tried both 32 & 64 bit Java (1.8) with no change in behavior for the most part.

 

Did you run into this error or any like it?

 

 

 

Any other hurdles with initial install, Java specific or any specific changes with server 'environment variables'?

 

Our environment required changes for 'Path' with the v9 agent related to Java path is why I ask.

 

[Fred Shindle]

Forgot, the install is on Windows 2012 R2 platform.

[Legacy User]

Hi FredS ,

You replaced the /appserver:9000 with the "real" PeopleSoft server name? Just to make sure. I can also create an incident for you to receive the full log file. Please let me know.

Cheers,
Alexander

[Legacy User]

P.S.: I installed them on Windows Server 2012 R2 and Linux 7.1.

I have JAVA_HOME set and JAVA_HOME/bin in the path. No other path is required to point to the jvm.dll anymore like it was in older versions of the PeopleSoft agent.

[Fred Shindle]

I have the “real” appserver:port defined, I just changed for forum posting. Did you run into any configuration issues within the ‘ini’ file, server environment variables or java paths or anything like that? I know for the v9 agent it was Java finicky, did you have any issues with Java related items. I have 32 bit JRE installed and 64 bit JDK & JRE, so the agent is using the 64 bit. From: Alexander Trenker [mailto:[e-mail]] Sent: Tuesday, June 27, 2017 9:14 PM To: Shindle, Fred

[Fred Shindle]

I will assume 'JAVA_HOME' being set at server level for environment variable and what is it set to?

Java 64 bit JDK or JRE bin?  Or is it 32 bit Java? 

[Legacy User]

JAVA_HOME is set to C:\Program Files\Java\jdk1.8.0_101 , so 64bit JDK. I can try it with a JDE tomorrow since JDK is not a prerequisite.
The 32bit requirement is definitely gone.

[Fred Shindle]

I thought the 32 bit requirement was gone, will verify for the Java UI when I get that far.

I uninstalled the JDK testing as the install only lists JRE but will see after testing if I need to re-install JDK as that was previously also required.

Is your JAVA_HOME defined as the first value in the "Path" environment variable?  I am guessing so as that is how our old 32 bit definition was.

Thanks for information, will let you know testing results.

[Legacy User]

Yes, my JAVA_HOME/bin is defined as the first value in the PATH.

[Fred Shindle]

Still no luck with this.

I get the same error with any combination of 32 or 64 bit, JDK or JRE, including the environment variable defined with 'bin' directory in the beginning of the string.

[John Torres]

FredS I don't have any experience with v12 yet but I had similar issues with v9 and each time it was something different....one time we fixed it by including a psmanagement file.
classes=psjoa.jar;UCXJPS84.jar;psmanagement.jar

[Fred Shindle]

John, Appreciate the post and feedback, was beginning to think no one else was even running PeopleSoft agent or folks were just sticking to previous versions. I really believe I am one of if not the first customer to try the v12 agent. There is a big difference in the agent functions and drivers. The PeopleSoft agent since our first install has always been a unique and never consistent configuration just as you state. Thanks again. From: John Torres [mailto:[e-mail]] Sent: Thursday, July 06, 2017 9:44 AM To: Shindle, Fred

[John Torres]

FredS we're a PS shop so this is also important for us. Please let me know how it goes and how your issue was resolved. We went from one PS App running on Windows and another on Unix to all on Unix. I know your issues are on Windows but I'm still interested in hearing the outcome. Thanks!  

[Fred Shindle]

No news for interested parties, we are still unable to configure correctly and/or start with original error.

[Christine Bauder]

Hello, not sure if you have solved this or not. We run Peoplesoft and we upgraded from v10 to v12 at the end of March. We ran into the same error with PS agents. This is from our ticket with support and the solution is at the bottom. Once we encrypted the password, everything came up.....

Subject

Errors Booting PeopleSoft Agent with v12.0.1

Description

20170217/144848.632 - U02007018 'DOWNbea.jolt.ServiceException: Invalid Session'  20170217/144848.633 - U02007010 Error connecting to the Application Server 'qfinapp07.qa.cu.edu:9033' and user 'CU_PRDSVCSYS'  Hello, I am getting the error above when trying to boot PeopleSoft agents in my newly upgraded v12 system. I can successfully start PeopleSoft agents on machines running RHEL6 and PeopleTools 8.54. This error occurs on RHEL7 machines running PeopleTools 8.55/  Things I have done:  1. Both systems use domain connection passwords and they are successful in 8.54.  2. Verified domain connection password on PS application server and UC4 agent config  3. stopped iptables on the agent machine to rule it out. We run iptables only on the RHEL7 servers  4. psjoa.jar is in the agents/peoplesoft/bin directory  5. Verified the password for CU_PRDSVCSYS is good in the login object and PeopleSoft database  What else can I be missing?

Suggested Solution

Hi Eric,  Thank you for the provided files. I see that you mention utilizing a Domain Connection Password, but I see the following in your logs:  20170217/144848.186 - ; domain_Connection_Pwd: You can indicate the Domain Connection password here if it is used in PeopleSoft.  20170217/144848.186 - ; Note that the password must be encrypted.  20170217/144848.187 - ;  20170217/144848.187 - ;domain_Connection_Pwd=*** (my edit)  ---  I see what may be two potential issues:  1) The password may not be encrypted. If this is the case, I would recommend utilizing our Encryption Tool to facilitate that.  2) This item (domain_Connection_Pwd=) appears to be commented out in the Agent's .ini file (as denoted by the semicolon). Please remove this and attempt to start the Agent again.  Please let me know the results of this, and we will proceed with next steps as appropriate.

[Legacy User]

Hi ChristineBauder603411 ,

I just looked at this case and saw that this change fixed your problem.

Thank you.

Cheers,
Alexander

[Fred Shindle]

 

Update for forum.

 

Automic DEV support is engaged and looking at this.

 

Was found the domain connect password was not being passed in the connection string.

 

I have had one other customer post they are successfully running PeopleSoft agent/workload installed on Linux OS.

 

This issue has been on Windows 2012 R2 OS.

 

I will update when resolved.

 

[Fred Shindle]

Never circled back to update this with fix for folks that might be viewing.

This is working in our environment for PeopleSoft agent v12.0.5 and PeopleTools v8.54.

There are 2 items we had to fix.

The default agent 'ucxjpsx.ini' file has 'domain_Connection_Pwd=' this will not work, the file value MUST be all upper case, like "DOMAIN_CONNECTION_PWD=".

As stated by instruction and above conversation the actual password MUST be encrypted with utility.  When the utility encrypts the password it prefixes value with 2 'hyphens' "--".  These are corrupt and must be deleted and manually input (same value, 2 hyphens).

 

This resolved the 'U02007018 'DOWNbea.jolt.ServiceException: Invalid Session' issue.