My Oracle Support Banner

Deployment Manager Fails To Open When Front-End Web Server Used (Doc ID 1273661.1)

Last updated on FEBRUARY 13, 2020

Applies to:

Identity Manager - Version and later
Information in this document applies to any platform.
"Checked For Relevance on 30-Jul-2012"


When clicking on the Export or Import option under Deployments tab, the deployment manager window pops up but remains blank, and nothing is displayed.

Performing a HTTP header trace, 404 errors are seen, like the following:

GET /Nexaweb/ielib/sniffer.js HTTP/1.1
Accept: */*
Referer: https://<OIM_HOSTNAME>/xlWebApp/DeploymentManager/<TOKENID>&org.apache.struts.taglib.html.TOKEN=<TOKENID>
Accept-Language: en-us
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Connection: Keep-Alive

HTTP/1.1 404 Not Found
Date: Mon, 13 Dec 2010 23:29:06 GMT
Server: Oracle-Application-Server-11g
Content-Length: 188
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1


Front end server (such as Oracle HTTP Server or Apache) was configured in front of OIM application server. The /xlWebApp URL is being passed successful to the backend server. However, after this configuration is implemented, the Deployment Manager no longer works.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.