nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS 7.2.1a post install issue

Jenni

Hi All,

Thanks in advance for your replies. We have installed TS 7.2.1a on Win 2008 server. The UI comes us fine and we are able to log on to the TS. When we try to click on the 'CCPRO' link, from the Administration console, the URL changes to

http://hostname.amda.com:8080/iw-cc/command/iw.ccpro.switch_ui

We would link the URL to be
http://hostname.amda.com/iw-cc/command/iw.ccpro.switch_ui

Our customized menu links (perl files) does not execute if we have 8080 on the URL.

Here are the config settings in iw.cfg file.

[admin_console]
admin_host=dvnva151
admin_port=8080

[iwwebd]
default_protocol=http
http_port=80
https_port=443

can anyone tell us if there are any changes that needs to be done for our issue?

Thanks!

Find more posts tagged with

Comments

Rick Poulin

I think the issue may be that your admin_host isn't set to localhost. In my iw.cfg, I have the following:

[HTML][admin_console]
admin_host=localhost
admin_port=8080

[iwwebd]
default_protocol=http
http_port=80
https_port=443
host=dvnva151[/HTML]

I think maybe since your admin_host is specified as a server name, TS has to assume that it's a different server and that may be the cause of the odd link behaviour. I can't think of any reason why your admin console wouldn't be on the same server as TS, so try modifying your config as above.

If that still doesn't work, did you make any special changes to IIS/Apache and/or iwproxy config?

nipper

****deleted, misread the issue******

Bowker

in 7.2.1 I added a line in iwwebd.cfg in (near line 232) that reads:
Listen 10.xx.xx.xx:80

(replace 10.xx.xx.xx with the IP address of your server)

and in iw.cfg
[iwwebd]
http_port=80
host=xxxxxxx

replace xxxxxxx with your server name.
That worked for us.

mart2001

Did you also try to use a fqdn?

Jenni

I think the issue may be that your admin_host isn't set to localhost. In my iw.cfg, I have the following:

[HTML][admin_console]
admin_host=localhost
admin_port=8080

[iwwebd]
default_protocol=http
http_port=80
https_port=443
host=dvnva151[/HTML]

I think maybe since your admin_host is specified as a server name, TS has to assume that it's a different server and that may be the cause of the odd link behaviour. I can't think of any reason why your admin console wouldn't be on the same server as TS, so try modifying your config as above.

If that still doesn't work, did you make any special changes to IIS/Apache and/or iwproxy config?

hi,

I changed the hostname to localhost, still same issue. Whenever we click on the Administration link, it is prompting us for entering our credentials.

We never made any change to IIS or Apache.

Thanks

Jenni

in 7.2.1 I added a line in iwwebd.cfg in (near line 232) that reads:
Listen 10.xx.xx.xx:80

(replace 10.xx.xx.xx with the IP address of your server)

and in iw.cfg
[iwwebd]
http_port=80
host=xxxxxxx

replace xxxxxxx with your server name.
That worked for us.

Hi,

I made your suggessted changes. The is no affect due to the changes. Any other pointer?

Thanks

Jenni

Did you also try to use a fqdn?

Hi,

What is fqdn?

Thanks

Rick Poulin

What is fqdn?

fully qualified domain name, eg. myserver.mycompany.org

Are you restarting the services (via iwreset -a) after each of these changes? It seems like at least one of the above suggestions should have had *some* effect.

Jenni

Hi rpoulin,

I tried fqdn and did iwreset -a. No affect though. Not sure how 8080 gets added in the URL.

Thanks

example2.rptdesign

nipper

You may want to change iwwebd.conf.template and use something like

Listen XX.XX.XX.XXlithium_IWWEBD_HTTP_PORT__

and then run iwreset -ui

That should change iwwebd.conf

Jenni

Is this format you suggessted?

Listen 12.44.34.123:80

nipper

Yea, the __IWWEB..... is replaced with 80 (or whatever port you have specified). Use your attempt to see, and if it works, then you can make it generic later.

Not that anyone will really be changing the port from 80.

Jenni

Nipper,

This was the value already existing. I had made this change as per bowker suggesstion.

Thanks

nipper

did you do it to iwwebd.conf or iwwebd.conf.template ?

The post I read was to do .conf, I suggested .template (and run iwreset -ui)

Jenni

I did it in both files. The .conf was not affected by the change in .template even after resetting the UI. So i edited both the files and restarted the box.

Thanks

Migrateduser

If you do a view source on the upper right corner while in Administration you will see that all the CCPro link does is this.

[PHP]
window.location.href = '/iw-cc/command/iw.ccpro.switch_ui';
[/PHP]

It only has a relative url. So it changing to 8080 isn't possible unless your admin url already contains 8080. If you see a full url when viewing source, then that is something different.

Do this, login to your server (http://hostname.amda.com) and watch to see when your port number changes as you are clicking along and let us know the results.

Also, upload your iw.cfg file. We need to see it's contents so we can quit guessing as to your settings.

Jenni

Hi Taalgaard,

When I try to log on to the CCPRO UI and do a view source, I see below code.


 ..id="iw.ccpro.common.actions_top_actionlist.switch_ui_admin.link" target="_top" title="Switch to Administration" href="/iw-cc/command/iw.ccpro.switch_ui_admin" iw_enabled="true"

When I click on the 'Administration' link, the url changes(by appending 8080) and I get prompted to enter my credentials. Once I enter my credentails, I see the the admin UI and then when I click on the CCPRO link, the UI switches to the CCPRO UI but the 8080 port number remains in the URL.

You are correct on your assumptions on the links.

We had buid anothere instance of the 7.2.1a server(d2) and moved the iw.cfg file from the server(d1) that currently has the adminstration link issue. We observed that the d2 server operates with out any issue. So we can conclude that the settings in iw.cfg file is not the issue.

Thanks

Migrateduser

Use a tool like Beyond Compare to do a directory comparison of iwhome using d1 and d2 to find what files are different and then look into those files to find the differences. You'll find out what config file is different that way.

Jenni

Thanks for that advice. We did the diff and there were no noticable differences.

We found out there was a mismatch on the TeamSite version.

50 REL Interwoven 20101026
102 REL Interwoven 20110321(this had the admin issue)

Have any one else installed 7.2.1a version and has the same issue we are experiencing?

Migrateduser

Nope, I'm running 7.2.1 Build 50 Interwoven 20101026