My company is upgrading from Agile PLM 9214 to 93. At the same time we are migrating from Oracle Application Server (OAS) to Weblogic (WLS).
In front of the servers is a Big IP LTM 1600, v 9.4.6 Build 401.0 Final.
The WLS environment consists of
(1) node manager server.
(2) managed servers.
(1) file manager server.
There are two clients for the user to login with: web and java. The web client works fine.
The java client, when going through the LTM, does not.
It does work connecting directly to either of the managed servers. This does give us some options for our small in number but noisy java client users, but we loose the LTM functions of availability and traffic management - we'd like to have those.
This is what happens:
User connects to the page with the link to launch the .jnlp file. http://agl.plexus.com:7001/JavaClient/start.html
Clicks 'launch'. WLS sends the .jnlp file to the client, which opens Java Web Start.
A login widget displays. Enter valid credentials.
After 90 seconds this error displays: Server is not valid or is unavailable.
I've got a ticket (C688392) open with support, they've got snoop captured packets from the server's POV of a session that works connecting directly to a managed server, and tcpdump captures of the malf'd session.
Anyone have experience w/ Agile PLM, Weblogic and the java client?
This is the jnlp file.
<!-- href="pcclient.jnlp" --> <!-- ref. sun's bug Id 4880785 -->
Agile 9.3.0.1
Oracle Corporation
Agile 9.3.0.1
Agile 9.3.0.1 Product Lifecycle Management (PLM)
serverURL=t3://agl.plexus.com:7001
jvuecodebase=http://://jVue
jvueserver=http://agl.plexus.com/Agile/VueServlet
installationinfo=/opt/agl/agile93/agsetup.enc
serverType=wls
tunneling.shortcut=true
webserverName=agl.plexus.com
appserverVersion=10.3
UpdateVersions=9.3.0.1
useSessionGenerator=true