ApplicationXtenter Infrastructure Deployment Notes

It seems that I did not take good notes on how to install and configure ApplicationXtender server components. Bah… this made for some fun when rebuilding the test environment. Here goes…

  1. Install Windows Server 2003, Standard Edition, with IIS. 
  2. Bring up to current patch level
  3. Install Oracle Client software…
  4. we used with all patches present on the Prod servers. 
    1. This requires several passes though the Oracle Universal Installer.  First a “runtime” install, then run through again to install “Windows Support Components”, which includes the ODBC drivers that are needed for AppXtender.
    2. Then we need to do two more passes though OUI to install patches, then drop in a few patched DLLs, and finally copy the TNSNames.ORA file from the oracle home on Prod servers to the NETWORK\Admin folder in the Oracle Home on this server.
    3. Update for 2009 – We are now using the database client, but installation is still pretty much the same… you still need the annoying Oracle Universal Installer, you still have to run OUI two to three times.  Additionally, our DBA team has switched from use of the “TNSNames.ORA” file, to “SQLNet.ORA” and “LDAP.ORA”.  Data Source names are now retrieved from an LDAP lookup.  So, ditch the TNSNames file, drop in the new ones.  Also, you must now request a firewall exemption to the database server to make this connection.  Plan a day ahead of time to get access.
  5. Create XS_Global service account, or use existing one. 
    1. Add this account to the local administrators group
    2. Add the additional rights “Act as part of the operating system”, “log on as a service”, and “replace a process level token” rights using the Local Security Policy MMC tool.
  6. Install Legato Licensing Server (if needed… we did not need a new one this time around
  7. Install DiskXtender 2000.  Use existing licensing server if available.  You will need to create service accounts for DX.
    1. Start DX Administrator… you must be a Domain Admin or the local Administrator account.  Members of local Admins have no rights to the DX console!
    2. Extend the local drive that will house your images by going to service->new extended drive.  There are no additional settings that need to be configured here
    3. Under “Service” select “properties”, then “Settings”, and “Partition Map”.
    4. Click “New”, then defined mappings for “DXTEST” (or whatever name you want to give to your DX Instance).  There will ony be one option to choose from under the “Extended Drive” drop-down.
    5. Add another mapping to “OBJECTS”, which will be the subdirectory created by AX in the DX repository.
    6. On the Prod server, we also did the following: Run RegEdit, navigate to:
      Then Modify “TcpIpEndpoint” from 1050 to 6252. This will force DX to use a port that can be accessed from the campus LAN.
  8. Install all AX Binaries… Includes AX Administration tools, ApplicationXtender Administrative installation, WebXtender, Rendering Server, ApplicatonXtender Web Services (IIS Mode).
  9. Open the “System” control panel item.  Go to “advanced”, and under “performance”, click “settings”.  Go to the “Data Execution Prevention” tab, and add an exception for %ProgramFiles%\XtenderSolutions\Content Management\Render Server\WxRender.exe.  This prevents the renderer from crashing in a Server 2003 SP1 environment.
  10. Create shares for “rendering” and “wxsession”.  Both shared need to be accessed Read/Write by the XS Service account.  These allow the rendering service and webXtender service, respectively, to cache files that may need to be accessible to other servers in the AX infrastructure.
  11. Use the “data source selector” tool in the ApplicationXtender Program Group.  Define sources for IMGX and IMGY (test and pre-prod data sources).  You will need to specify the “server name” as “”, and “”, as this is how they are defined in the TNSNames file.  Note that you MUST use the Microsoft OLE DB Provider for Oracle, not the raw Oracle ODBC driver! 
  12. Start XtenderSolutions Administrator (XSAdmin forthwith). 
    1. Login as SYSOP user.
    2. On a new install, you would need to define “Windows Security” as the Security Model in the initial “Environment->Data Sources” window.
    3. Under “Storage->DiskXtender”, we need to have defined:
      Server Name=DXTEST, Connection Type=RPC, DX Network Address=DOCIMGTEST, Network Transport=TCP/IP. Also, on the Prod server, we have defined the “end point” port as 6252.
    4. Under “Storage->Paths”, make sure that any defined paths are valid. It is here that we define the connection to the “rendering” and “wxsession” shares that were created earlier.
    5. Under “WebXtender->Setup”, you must define the service account, and under “Email” you need to specify “” as the email server, then define a “from” address for the service.
    6. Under “Services->Rendering Server”, you again need to define a service account, then provide the “rendering” share created above as the Cache “location”.
    7. Under “Services->XS Web Services”, define a service account.
  13. Run “User Profile Administrator” in the XtenderSolutions Program Group. We set our users to NOT use the Interactive Client by default. However, using AppGen we have given all users the ability to change this setting.
  14. Run the “Component Setup Wizard” in the XtenderSolutions Program Group. Run through the wizard for each component in the infrastructure (XS Web, WebXtender, Rendering Server).
  15. Updated for 2009 – IIS Tuning:
    1. In IIS Admin, get properties on the default web site, access the “Directory Security” tab, and install a server certificate.
    2. Click “Edit” to require SSL for the site
    3. Go to the “Custom Errors” tab, and add our standard JavaScript redirect html file in place of the 403.4 error page… this will force users over to the SSL version of the site using a javascript redirect, instead of displaying an ugly error page.
    4. On the “Home Directory” tab, add a permanent redirect from the base web site URL to the “/AppXender” subdirectory
    5. Get properties on the /AppXtender subdirectory.  In the “Documents” tab, add “Default.aspx” as a default content page.  Failure to do so will result in an “403.14” error page.

Leave a Reply