Topic
  • 11 replies
  • Latest Post - ‏2012-10-03T14:16:52Z by eckertd
eckertd
eckertd
7 Posts

Pinned topic Remote administration of ILMT

‏2012-09-28T15:07:15Z |
Greetings. Just finished installing ILMT/DB2/eWAS in a Windows 2008R2 environment. I've got a couple agents installed and reporting just fine. It's running in test/POC mode.

My issue is how to get it listening on the primary IP address of the server for remote administration. Right now, it's only listening on 'localhost:16311' Can someone point me in the right direction? Thanks in advance!
Updated on 2012-10-03T14:16:52Z at 2012-10-03T14:16:52Z by eckertd
  • SystemAdmin
    SystemAdmin
    340 Posts

    Re: Remote administration of ILMT

    ‏2012-09-28T15:39:04Z  
    Hello,

    It must be a problem of Windows firewall. We do not block remote connections to the console.
    Please check the firewall settings.

    Regards
  • MaksKowalik
    MaksKowalik
    78 Posts

    Re: Remote administration of ILMT

    ‏2012-09-28T15:43:32Z  
    Hi,

    the Websphere server should listen on all addresses. Could you please paste the output of netstat -anop tcp here?

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
  • eckertd
    eckertd
    7 Posts

    Re: Remote administration of ILMT

    ‏2012-09-28T18:44:47Z  
    Hi,

    the Websphere server should listen on all addresses. Could you please paste the output of netstat -anop tcp here?

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    My mistake, it is listening on all(0.0.0.0) interfaces, see below. However, when I try to access it remotely, I get:

    SRVE0255E: A WebGroup/Virtual Host to handle / has not been defined.

    It doesn't matter if I try http or https, same result. Might this be a function of it being in test/POC mode? Firewall service is disabled.

    P:\>netstat -naop tcp

    Active Connections

    Proto Local Address Foreign Address State PID
    TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 652
    TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:523 0.0.0.0:0 LISTENING 260
    TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1372
    TCP 0.0.0.0:9977 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:9988 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:9999 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16310 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16311 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16312 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16313 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16315 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16316 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16318 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16320 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16321 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16322 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 364
    TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 752
    TCP 0.0.0.0:50000 0.0.0.0:0 LISTENING 3832
    TCP 0.0.0.0:51719 0.0.0.0:0 LISTENING 1724
    TCP 0.0.0.0:60434 0.0.0.0:0 LISTENING 1192
    TCP 0.0.0.0:60436 0.0.0.0:0 LISTENING 460
    TCP 0.0.0.0:60452 0.0.0.0:0 LISTENING 452
    TCP 0.0.0.0:62663 0.0.0.0:0 LISTENING 800
    TCP 127.0.0.1:6999 0.0.0.0:0 LISTENING 2448
    TCP 127.0.0.1:6999 127.0.0.1:62631 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62634 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62639 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62641 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62643 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62646 ESTABLISHED 2448
    TCP 127.0.0.1:16314 0.0.0.0:0 LISTENING 2052
    TCP 127.0.0.1:50000 127.0.0.1:62178 ESTABLISHED 3832
    TCP 127.0.0.1:50000 127.0.0.1:62799 ESTABLISHED 3832
    TCP 127.0.0.1:50000 127.0.0.1:64199 ESTABLISHED 3832
    TCP 127.0.0.1:60434 127.0.0.1:60668 ESTABLISHED 1192
    TCP 127.0.0.1:60668 127.0.0.1:60434 ESTABLISHED 872
    TCP 127.0.0.1:61887 127.0.0.1:61888 ESTABLISHED 2052
    TCP 127.0.0.1:61888 127.0.0.1:61887 ESTABLISHED 2052
    TCP 127.0.0.1:62178 127.0.0.1:50000 ESTABLISHED 2052
    TCP 127.0.0.1:62631 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62633 127.0.0.1:6999 TIME_WAIT 0
    TCP 127.0.0.1:62634 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62635 127.0.0.1:6999 TIME_WAIT 0
    TCP 127.0.0.1:62639 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62641 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62643 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62646 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62799 127.0.0.1:50000 ESTABLISHED 2052
    TCP 127.0.0.1:64199 127.0.0.1:50000 ESTABLISHED 2052
    TCP 172.26.23.218:3389 172.26.101.58:2608 ESTABLISHED 1372
    TCP 172.26.23.218:60561 172.26.23.212:443 ESTABLISHED 1504
    TCP 172.26.23.218:62612 184.31.50.189:443 ESTABLISHED 3116
    TCP 172.26.23.218:62613 184.31.50.24:443 ESTABLISHED 3116
    TCP 172.26.23.218:62615 172.26.183.11:445 ESTABLISHED 4
    TCP 172.26.23.218:62616 172.26.23.163:445 ESTABLISHED 4
    TCP 172.26.23.218:62619 172.26.184.43:135 TIME_WAIT 0
    TCP 172.26.23.218:62620 172.26.184.43:1025 ESTABLISHED 460
    TCP 172.26.23.218:62621 172.26.184.43:389 TIME_WAIT 0
    TCP 172.26.23.218:62628 172.26.184.43:389 TIME_WAIT 0
    TCP 172.26.23.218:62629 10.0.64.6:389 TIME_WAIT 0
    TCP 172.26.23.218:62630 10.0.64.6:389 TIME_WAIT 0
    TCP 172.26.23.218:62632 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62636 129.42.60.216:80 TIME_WAIT 0
    TCP 172.26.23.218:62637 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62638 129.42.60.216:80 TIME_WAIT 0
    TCP 172.26.23.218:62640 184.31.50.189:80 ESTABLISHED 2448
    TCP 172.26.23.218:62642 184.31.50.189:80 ESTABLISHED 2448
    TCP 172.26.23.218:62644 184.31.50.24:80 ESTABLISHED 2448
    TCP 172.26.23.218:62645 129.42.60.216:443 TIME_WAIT 0
    TCP 172.26.23.218:62647 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62648 129.42.60.216:443 ESTABLISHED 3652
  • SystemAdmin
    SystemAdmin
    340 Posts

    Re: Remote administration of ILMT

    ‏2012-09-29T07:36:04Z  
    • eckertd
    • ‏2012-09-28T18:44:47Z
    My mistake, it is listening on all(0.0.0.0) interfaces, see below. However, when I try to access it remotely, I get:

    SRVE0255E: A WebGroup/Virtual Host to handle / has not been defined.

    It doesn't matter if I try http or https, same result. Might this be a function of it being in test/POC mode? Firewall service is disabled.

    P:\>netstat -naop tcp

    Active Connections

    Proto Local Address Foreign Address State PID
    TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 652
    TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:523 0.0.0.0:0 LISTENING 260
    TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1372
    TCP 0.0.0.0:9977 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:9988 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:9999 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16310 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16311 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16312 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16313 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16315 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16316 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16318 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16320 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16321 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16322 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 364
    TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 752
    TCP 0.0.0.0:50000 0.0.0.0:0 LISTENING 3832
    TCP 0.0.0.0:51719 0.0.0.0:0 LISTENING 1724
    TCP 0.0.0.0:60434 0.0.0.0:0 LISTENING 1192
    TCP 0.0.0.0:60436 0.0.0.0:0 LISTENING 460
    TCP 0.0.0.0:60452 0.0.0.0:0 LISTENING 452
    TCP 0.0.0.0:62663 0.0.0.0:0 LISTENING 800
    TCP 127.0.0.1:6999 0.0.0.0:0 LISTENING 2448
    TCP 127.0.0.1:6999 127.0.0.1:62631 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62634 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62639 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62641 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62643 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62646 ESTABLISHED 2448
    TCP 127.0.0.1:16314 0.0.0.0:0 LISTENING 2052
    TCP 127.0.0.1:50000 127.0.0.1:62178 ESTABLISHED 3832
    TCP 127.0.0.1:50000 127.0.0.1:62799 ESTABLISHED 3832
    TCP 127.0.0.1:50000 127.0.0.1:64199 ESTABLISHED 3832
    TCP 127.0.0.1:60434 127.0.0.1:60668 ESTABLISHED 1192
    TCP 127.0.0.1:60668 127.0.0.1:60434 ESTABLISHED 872
    TCP 127.0.0.1:61887 127.0.0.1:61888 ESTABLISHED 2052
    TCP 127.0.0.1:61888 127.0.0.1:61887 ESTABLISHED 2052
    TCP 127.0.0.1:62178 127.0.0.1:50000 ESTABLISHED 2052
    TCP 127.0.0.1:62631 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62633 127.0.0.1:6999 TIME_WAIT 0
    TCP 127.0.0.1:62634 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62635 127.0.0.1:6999 TIME_WAIT 0
    TCP 127.0.0.1:62639 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62641 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62643 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62646 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62799 127.0.0.1:50000 ESTABLISHED 2052
    TCP 127.0.0.1:64199 127.0.0.1:50000 ESTABLISHED 2052
    TCP 172.26.23.218:3389 172.26.101.58:2608 ESTABLISHED 1372
    TCP 172.26.23.218:60561 172.26.23.212:443 ESTABLISHED 1504
    TCP 172.26.23.218:62612 184.31.50.189:443 ESTABLISHED 3116
    TCP 172.26.23.218:62613 184.31.50.24:443 ESTABLISHED 3116
    TCP 172.26.23.218:62615 172.26.183.11:445 ESTABLISHED 4
    TCP 172.26.23.218:62616 172.26.23.163:445 ESTABLISHED 4
    TCP 172.26.23.218:62619 172.26.184.43:135 TIME_WAIT 0
    TCP 172.26.23.218:62620 172.26.184.43:1025 ESTABLISHED 460
    TCP 172.26.23.218:62621 172.26.184.43:389 TIME_WAIT 0
    TCP 172.26.23.218:62628 172.26.184.43:389 TIME_WAIT 0
    TCP 172.26.23.218:62629 10.0.64.6:389 TIME_WAIT 0
    TCP 172.26.23.218:62630 10.0.64.6:389 TIME_WAIT 0
    TCP 172.26.23.218:62632 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62636 129.42.60.216:80 TIME_WAIT 0
    TCP 172.26.23.218:62637 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62638 129.42.60.216:80 TIME_WAIT 0
    TCP 172.26.23.218:62640 184.31.50.189:80 ESTABLISHED 2448
    TCP 172.26.23.218:62642 184.31.50.189:80 ESTABLISHED 2448
    TCP 172.26.23.218:62644 184.31.50.24:80 ESTABLISHED 2448
    TCP 172.26.23.218:62645 129.42.60.216:443 TIME_WAIT 0
    TCP 172.26.23.218:62647 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62648 129.42.60.216:443 ESTABLISHED 3652
    Could you please send us the following logs:
    1. <lmt_install_dir>\resume\LMT<version>\<install_time_stamp>\Server.log
    2. <system_dir>\tmp\ia.log
    3. <home_dir>\TIP*.log

    I would like to check if the installation went fine.

    Thank You
  • MaksKowalik
    MaksKowalik
    78 Posts

    Re: Remote administration of ILMT

    ‏2012-09-29T07:53:25Z  
    • eckertd
    • ‏2012-09-28T18:44:47Z
    My mistake, it is listening on all(0.0.0.0) interfaces, see below. However, when I try to access it remotely, I get:

    SRVE0255E: A WebGroup/Virtual Host to handle / has not been defined.

    It doesn't matter if I try http or https, same result. Might this be a function of it being in test/POC mode? Firewall service is disabled.

    P:\>netstat -naop tcp

    Active Connections

    Proto Local Address Foreign Address State PID
    TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 652
    TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:523 0.0.0.0:0 LISTENING 260
    TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1372
    TCP 0.0.0.0:9977 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:9988 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:9999 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16310 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16311 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16312 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16313 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16315 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16316 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16318 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16320 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16321 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:16322 0.0.0.0:0 LISTENING 2052
    TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
    TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 364
    TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 752
    TCP 0.0.0.0:50000 0.0.0.0:0 LISTENING 3832
    TCP 0.0.0.0:51719 0.0.0.0:0 LISTENING 1724
    TCP 0.0.0.0:60434 0.0.0.0:0 LISTENING 1192
    TCP 0.0.0.0:60436 0.0.0.0:0 LISTENING 460
    TCP 0.0.0.0:60452 0.0.0.0:0 LISTENING 452
    TCP 0.0.0.0:62663 0.0.0.0:0 LISTENING 800
    TCP 127.0.0.1:6999 0.0.0.0:0 LISTENING 2448
    TCP 127.0.0.1:6999 127.0.0.1:62631 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62634 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62639 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62641 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62643 ESTABLISHED 2448
    TCP 127.0.0.1:6999 127.0.0.1:62646 ESTABLISHED 2448
    TCP 127.0.0.1:16314 0.0.0.0:0 LISTENING 2052
    TCP 127.0.0.1:50000 127.0.0.1:62178 ESTABLISHED 3832
    TCP 127.0.0.1:50000 127.0.0.1:62799 ESTABLISHED 3832
    TCP 127.0.0.1:50000 127.0.0.1:64199 ESTABLISHED 3832
    TCP 127.0.0.1:60434 127.0.0.1:60668 ESTABLISHED 1192
    TCP 127.0.0.1:60668 127.0.0.1:60434 ESTABLISHED 872
    TCP 127.0.0.1:61887 127.0.0.1:61888 ESTABLISHED 2052
    TCP 127.0.0.1:61888 127.0.0.1:61887 ESTABLISHED 2052
    TCP 127.0.0.1:62178 127.0.0.1:50000 ESTABLISHED 2052
    TCP 127.0.0.1:62631 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62633 127.0.0.1:6999 TIME_WAIT 0
    TCP 127.0.0.1:62634 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62635 127.0.0.1:6999 TIME_WAIT 0
    TCP 127.0.0.1:62639 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62641 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62643 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62646 127.0.0.1:6999 ESTABLISHED 3652
    TCP 127.0.0.1:62799 127.0.0.1:50000 ESTABLISHED 2052
    TCP 127.0.0.1:64199 127.0.0.1:50000 ESTABLISHED 2052
    TCP 172.26.23.218:3389 172.26.101.58:2608 ESTABLISHED 1372
    TCP 172.26.23.218:60561 172.26.23.212:443 ESTABLISHED 1504
    TCP 172.26.23.218:62612 184.31.50.189:443 ESTABLISHED 3116
    TCP 172.26.23.218:62613 184.31.50.24:443 ESTABLISHED 3116
    TCP 172.26.23.218:62615 172.26.183.11:445 ESTABLISHED 4
    TCP 172.26.23.218:62616 172.26.23.163:445 ESTABLISHED 4
    TCP 172.26.23.218:62619 172.26.184.43:135 TIME_WAIT 0
    TCP 172.26.23.218:62620 172.26.184.43:1025 ESTABLISHED 460
    TCP 172.26.23.218:62621 172.26.184.43:389 TIME_WAIT 0
    TCP 172.26.23.218:62628 172.26.184.43:389 TIME_WAIT 0
    TCP 172.26.23.218:62629 10.0.64.6:389 TIME_WAIT 0
    TCP 172.26.23.218:62630 10.0.64.6:389 TIME_WAIT 0
    TCP 172.26.23.218:62632 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62636 129.42.60.216:80 TIME_WAIT 0
    TCP 172.26.23.218:62637 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62638 129.42.60.216:80 TIME_WAIT 0
    TCP 172.26.23.218:62640 184.31.50.189:80 ESTABLISHED 2448
    TCP 172.26.23.218:62642 184.31.50.189:80 ESTABLISHED 2448
    TCP 172.26.23.218:62644 184.31.50.24:80 ESTABLISHED 2448
    TCP 172.26.23.218:62645 129.42.60.216:443 TIME_WAIT 0
    TCP 172.26.23.218:62647 129.42.60.216:80 ESTABLISHED 2448
    TCP 172.26.23.218:62648 129.42.60.216:443 ESTABLISHED 3652
    Hi,

    are you trying
    https://IP_address_of_the_server:16311/
    ?

    The ILMT application is available on https://IP_address_of_the_server:16311/ibm/console

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
  • eckertd
    eckertd
    7 Posts

    Re: Remote administration of ILMT

    ‏2012-10-02T18:22:18Z  
    Could you please send us the following logs:
    1. <lmt_install_dir>\resume\LMT<version>\<install_time_stamp>\Server.log
    2. <system_dir>\tmp\ia.log
    3. <home_dir>\TIP*.log

    I would like to check if the installation went fine.

    Thank You
    Server.log attached. Thanks for the second set of eyes.

    Attachments

  • eckertd
    eckertd
    7 Posts

    Re: Remote administration of ILMT

    ‏2012-10-02T18:25:03Z  
    Could you please send us the following logs:
    1. <lmt_install_dir>\resume\LMT<version>\<install_time_stamp>\Server.log
    2. <system_dir>\tmp\ia.log
    3. <home_dir>\TIP*.log

    I would like to check if the installation went fine.

    Thank You
    ia.log attached.

    Attachments

  • eckertd
    eckertd
    7 Posts

    Re: Remote administration of ILMT

    ‏2012-10-02T18:27:48Z  
    Could you please send us the following logs:
    1. <lmt_install_dir>\resume\LMT<version>\<install_time_stamp>\Server.log
    2. <system_dir>\tmp\ia.log
    3. <home_dir>\TIP*.log

    I would like to check if the installation went fine.

    Thank You
    TIPInstaller log attached.
  • eckertd
    eckertd
    7 Posts

    Re: Remote administration of ILMT

    ‏2012-10-02T18:31:25Z  
    Hi,

    are you trying
    https://IP_address_of_the_server:16311/
    ?

    The ILMT application is available on https://IP_address_of_the_server:16311/ibm/console

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    > are you trying
    > https://IP_address_of_the_server:16311/ ?

    Yes. I've tried all combinations of http, https with ports 16310 and 16311.
  • MaksKowalik
    MaksKowalik
    78 Posts

    Re: Remote administration of ILMT

    ‏2012-10-02T20:01:23Z  
    • eckertd
    • ‏2012-10-02T18:31:25Z
    > are you trying
    > https://IP_address_of_the_server:16311/ ?

    Yes. I've tried all combinations of http, https with ports 16310 and 16311.
    I wasn't asking about ports & protocols, but about whole URL.
    If you are really trying https://IP_address_of_the_server:16311/ then you won't find ILMT application there (unfortunately, there's no redirection to the /ibm/console)

    The error
    SRVE0255E: A WebGroup/Virtual Host to handle / has not been defined.
    suggests that you did not type the whole url.

    Please try https://IP_address_of_the_server:16311/ibm/console
    and tell us what's the result.

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
  • eckertd
    eckertd
    7 Posts

    Re: Remote administration of ILMT

    ‏2012-10-03T14:16:52Z  
    I wasn't asking about ports & protocols, but about whole URL.
    If you are really trying https://IP_address_of_the_server:16311/ then you won't find ILMT application there (unfortunately, there's no redirection to the /ibm/console)

    The error
    SRVE0255E: A WebGroup/Virtual Host to handle / has not been defined.
    suggests that you did not type the whole url.

    Please try https://IP_address_of_the_server:16311/ibm/console
    and tell us what's the result.

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    Yep...that was it. Thanks!