CWS and DNS Alias

At our customers we typically have the CS services accessed via DNS alias rather than the direct server name; is there a straightforward way to configure CWS to present or use such an alias in place of the underlying hostname used by the OS?

The CS10 environment is W2K8R2 + IIS7.5 + Oracle.

Find more posts tagged with

Comments

eLink User

This is not specific to livelink but it is a IIS7 Binding (not sure if this is the same as HOST-HEADER) issue.If your servers are called mycompany.intranet.net then and it is distributed into a pool of serversA,B & C.

ServerA,B & C will have a IIS Binding called mycompany.intranet.net.Simply put if somebody request the URI mycompany.intranet.net it would route to one these 3 servers.

Then inside your livelink webservices Web.Config you would make a copy of it and add the binding like this

Basically this element is added <serviceHostingEnvironment>
<baseAddressPrefixFilters> and closed for proper xml

        </services>
    <serviceHostingEnvironment>
            <baseAddressPrefixFilters>
                   <add prefix="mycompany.intranet.net/"/>
            </baseAddressPrefixFilters>
        </serviceHostingEnvironment>
    </system.serviceModel>
</configuration>

Now for things that are relevant for coding and livelink.If you are seeking authentication using livelinks authservice and not OTCS(RCS) may it be known that when the client program executes,it receives a cookie (token in WSAPI parlance) from the livelink server A, B or C as your luck may be.If security params on livelink servers are at default ,then the client IP is part of the cookie,so if your LB puts the next call and it lands in Server B or C,you will get a "could not login by cookie" error.To avoid that people will put for WS a sticky session bit which means that the client always are talking to the same server which defeats the LB purpose.What can you do? OT will advise you to relax the rule of IP checking but I rarely accept their dictum as it becomes easy to spoof the livelink server.You have to seriously sit with your network team and come with a solution.OT also now uses "x-forwarded for" although i have never used it myself. You could have SSO with REMOTE_USER and get by that as well. Perhaps the OTCS tokens are coded for multiple servers/domains I know not.

..Appu

1 Use Share Point, 2 Use Web Report, 3 Use Spread Sheet

On Mon, Jan 6, 2014 at 3:50 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

CWS and DNS Alias Posted bysevans@datacentrix.co.za (D'Arcy-Evans, Stephen)On 01-06-2014 04:46

At our customers we typically have the CS services accessed via DNS alias rather than the direct server name; is there a straightforward way to configure CWS to present or use such an alias in place of the underlying hostname used by the OS? The CS10 environment is W2K8R2 + IIS7.5 + Oracle.
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center

Kyle_Swidrovich

The host resolution is done through the OS, so if the OS can resolve your entry, it should be able to connect.

Are you saying it doesn’t work when using a fully-qualified alias?

Kyle

Todd_Pinel

I believe what Stephen is referring to Kyle is that when you view the service description of a WCF service through the browser it will display the hostname of the server by default, this is also true for the WSDL.

To change this you can do what the other user suggested and change the base address prefix. You will probably also have to be explicit about your endpoint address values under the <endpoint> tag and the httpGetUrl value under the <behavior> tag for each service.