How work exactly the internal aliases in ICF

[Former Member]

Hi all,

I have small problem with internal aliases. I have a bsp application in SAP name space, so in SICF I can find it in this node:

<b>/sap/bc/bsp/sap/</b>

if I create an internal alias (in SICF transaction) in the node:

<b>/sap/bc/bsp/spt/</b> (it's normal that the last node is spt and not sap) when I call my URL I get this error message:

<b>BSP Exception: the Application Name myBspApplAlias in URL /sap/bc/bsp/spt/myBspApplAlias is invalid.</b>

I have checked that every node is active

Now I create an other internal alias in node <b>/sap/bc/</b>

and now it works fine.

So after some testing I have found that if the internal alias is created in a node deeper than <b>/sap/bc/</b> it doesn't work.

I would like to know if this behaviour is normal or not, and if it's possible for me to have an internal alias in node <b>/sap/bc/bsp/spt/</b> that point to an application in node <b>/sap/bc/bsp/sap/</b>.

Thanks in advance for all your response.

Best Regards

Jerome

[former_member181879]

Much more important is the node onto which the alias is pointing and how you use it in the browser!

For example, I created an alias "/sap/bc/bsp/xyz/" which points onto "/sap/bc/bsp/sap". In the browser I then called it with "/sap/bc/bsp/xyz/it00/default.htm". Effectively the URL from the browser is matched segment for segment against the alias onto a target node. And then there must still be enough tokens left to navigate through the original tree to your application.

It is a slightly complex material, and I would really in this case recommend the documentation. Should you suspect an error, OSS (CSN internal!) problem ticket onto BC-MID-ICF.

brian