Forum Discussion

vhv84_96225's avatar
vhv84_96225
Icon for Nimbostratus rankNimbostratus
Mar 27, 2014

Websphere Portal and webmaster access error

Dear all

 

I had Virtual Server 172.16.80.72 with pool 3 APP Webshpere 172.16.85.71:10039,172.16.85.72:10050, 172.16.85.73:10050. VS's irule redirect from http://172.16.80.72 to http://172.16.80.72/wcs/portal. After configuration, client access it well but webmaster has few complaints. After login to admin website, admin interface broken icons. When click the tab for system administrator, error message display "Google chrome could not connect http://172.16.80.72:10050/wcs/myportal". I want to use VS replace the edge server 172.16.80.32. If click the tab for system administrator on 172.16.80.32, access link is http://172.16.80.32/wcs/myportal. How to resolve problem ? I need config on F5 or request webmaster config for http response from server app to F5 auto change the service port from 10050 to 80.

 

Best Regard

 

application delivery
deployment
ibm
LTM
performance
  • vhv84_96225's avatar
    vhv84_96225
    Icon for Nimbostratus rankNimbostratus
    Apr 01, 2014

    Dear Cory I send configuration file of VS_website. I test with 1 member 172.16.85.71:10039. [root@DC-INT-BIGIP02:Active:In Sync] config tmsh list ltm virtual Website ltm virtual Website { destination 172.16.80.72:http ip-protocol tcp mask 255.255.255.255 persist { Cookie_Websitethue { default yes } } pool Website profiles { Profile_for_Website_Cache { } Profile_for_Website_Compress { } http { } oneconnect { } rewrite-uri-translation { } tcp-lan-optimized { context clientside } tcp-wan-optimized { context serverside } } rules { Irule_for_website irule_website_test } source 0.0.0.0/0 source-address-translation { type automap } vs-index 15 } [root@DC-INT-BIGIP02:Active:In Sync] config tmsh list ltm pool Website ltm pool Website { load-balancing-mode least-connections-member members { 172.16.80.78:10039 { address 172.16.80.78 session monitor-enabled state up } } monitor tcp and http } [root@DC-INT-BIGIP02:Active:In Sync] config tmsh list ltm virtual web71_10039 ltm virtual web71_10039 { destination 172.16.80.78:10039 ip-protocol tcp mask 255.255.255.255 pool web10039 profiles { http { } tcp { } } rules { Irule_for_website } source 0.0.0.0/0 vs-index 17 } [root@DC-INT-BIGIP02:Active:In Sync] config tmsh list ltm pool web10039 ltm pool web10039 { members { 172.16.85.71:10039 { address 10.64.85.71 monitor tcp session monitor-enabled state up } } } Best Regards

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Apr 01, 2014

    So your virtual server "Website" looks correct. You are listening on port 80 and translating to 10039 on your backend pool member.

     

    When users attempt HTTP connections to 172.16.80.72, do they work? If not, what are your two iRules doing?

     

  • vhv84_96225's avatar
    vhv84_96225
    Icon for Nimbostratus rankNimbostratus
    Apr 02, 2014

    Dear Cory

     

    I list 2 irule. Irule Irule_for_website attach to VS Website 10.64.80.72:80

     

     

    Irule irule_website_test has been removed. Sorry, i don't know how to display better config file on devcentral. Best regards

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Apr 02, 2014

    So what exactly is the behavior now when a user attempts a connection to http://172.16.80.72?

     

    First the user would get redirected to http://172.16.80.72/wps/portal, then what happens?