Forum Discussion

BDunbar_8799's avatar
BDunbar_8799
Icon for Nimbostratus rankNimbostratus
Jul 01, 2010

Agiile PLM - WebLogic - LTM

F5 LTM - BigIP version 9.4.6

 

Oracle Agile PLM

 

Two WebLogic managed hosts

 

 

I've got an install of Oracle's Agile PLM. This is built on their WebLogic (WLS) server. There are two managed hosts delivering bits to users.

 

 

Agile PLM comes with two clients - a browser client and java.

 

 

Browser client has an address like so:

 

http://agl.company.com:7001/Agile/default/login-cms.jsp

 

 

Java client has an adderss like so:

 

http://agl-java.company.com:7001/JavaClient/start.html

 

or

 

http://agl.company.com:7001/JavaClient/start.html

 

 

All users are internal, or will be acessing using VPN.

 

 

We go live in eight days.

 

 

 

In order to make the browser work through LTM I must have persistance on. In order to make the Java client work I must set the VS type to Performance (Layer 4).

 

 

 

 

To resolve the conflict between persistance and 'Performance (Layer 4)' I have established two host names:

 

 

agl.company.com. The VS that has this IP for a destination uses type = Standard and has persistence = cookie.

 

 

agl-java.company.com. The VS that has this IP for a destination uses type = Performance (Layer 4).

 

 

This works and is acceptable to the business owners.

 

 

But what I'd like to do, in an ideal world, is have both clients use the same address.

 

 

Is there a way to skin this cat?

 

config
design
  • L4L7_53191's avatar
    L4L7_53191
    Icon for Nimbostratus rankNimbostratus
    Jul 02, 2010
    Maybe. The trick with the java component is that it looks like it's using the t3 protocol, which is not all that common and why you need perf. L4 (that's my guess anyhow). From the looks of it though, you may be able to define the java service on another Virtual Server - same address, different port. This would of course mean that you'd need to change the definition in your JNLP file and possibly on the application side, but I'm not certain of that. You may just have the JNLP point to the domain name and new port, then point it to the same port on the back end at 7001.

     

     

    Just an idea that may or may not help, but may be worth a try if you've got some testing cycles left...

     

     

    -Matt
  • BDunbar_8799's avatar
    BDunbar_8799
    Icon for Nimbostratus rankNimbostratus
    Jul 02, 2010
    Matt,

     

     

    Thank you for your reply. I should have - but did not - think about changing the port address the java bits use. Seems so obvious in hindsight.

     

     

    Doing this is - for this application - should be simple. Halt, edit a file, restart.