Has or is anyone successfully installed and running the newest PeopleSoft agent, v12.0.2?
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.
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
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
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
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.
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?
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.
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.
No news for interested parties, we are still unable to configure correctly and/or start with original error.
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.
Retrieving data ...