June 2008 Archives

So you can't live with an url like http://company.com/portal/server.pt? Luckily, you've got options. This blog discusses in detail how you can change that URL with ALUI 6.1 MP1 P1. It more briefly explains how to do it on earlier and later versions too.

First take care of these prerequisites:

  • Install base ALUI 6.1 MP1
  • Install P1
  • Load portal at http://company.com/portal/server.pt. It works!
  • Because of a bug in MP1 related to alternate virtual directories, you need to also install the CF AquaLogicInteraction_6.1.1.325722. This does not apply to earlier or later releases. I'm sorry to say the only way to get that CF is to ask customer support for it. That's how CFs work.

But as we already decided, you don't like that default URL. You want to remove /portal entirely. So set up your machine with Metabase Explorer to easily copy your IIS config from the /portal virtual directory to your root directory. Metabase Explorer is part of the IIS Resource Toolkit available here.

Let's use it:

  • Launch Metabase Explorer (Start->IIS Resources->Metabase Explorer->Metabase Explorer).
  • Navigate the tree to the /portal virtual directory. This may be at LM/W3SVC/1/ROOT/portal.
  • Within /portal, right-click on ScriptMaps and copy.
  • Within /ROOT, right-click on ScriptMaps and paste.
  • Within /portal, right-click on Path and copy.
  • Within /ROOT, right-click on Path and paste.

Now you've got IIS configured. Let's move to the portal and get it squared away:

  • Open %ALUI_HOME%\settings\portal\portalconfig.xml and edit it to remove "portal/" from the following settings:
    • VirtualDirectoryPath
    • AdminSiteBaseURL
    • SSOVirtualDirectoryPath
  • Save the file
  • Restart IIS

You should now be able to browse to http://company/server.pt. It worked for me!

In the case of ALUI 6.5, I was able to do this without worrying about a CF. In the case of ALUI 6.1.0.1 and Plumtree 5.0.4, I never tried removing the /portal virtual directory entirely, but I was able to rename that directory without difficulty so I believe renaming the virtual directory to "/" will not pose a problem.

Finally, as a bonus, let's say you don't like the server.pt extension. On IIS it turns out, you can use anything that ends in .pt. So you might choose to publish your portal's URL as something more apt such as http://company.com/a.pt.

Please let me know how this works for you. These aren't battle tested instructions, and this may not be a "supported" configuration. If you deploy this and have many users hitting the portal on a sustained basis, let me know with a comment. Or if you find my instructions are buggy? Let me know that too.

Enjoy!