The scenario:

I have created a Service Interface. When I click "Deploy" to deploy the Service Interface I get the following results:

Starting deployment

Generating COBOL module

Compiling COBOL module

Compilation complete

Generating manifest

Generating the deployment package

Contacting the server

Sending deployment file to server

500: Unable to create unique directory "C:/Program Files (x86)/Micro Focus/Enterprise Developer/deploy/CICSScreenWs.s54O4TDc": Permission denied

I do not have administrative rights to put the deploy contents into the C:\\Program Files(x86) directory or any of its subdirectories.

 How can the  C:/Program Files (x86)/ directory be changed to another directory so this deployment can complete successfully ?

The upper-level directory can be changed in this way:

The top-level deployment directory is configured in the deployment service and its associated listener.

The resolution:

The top-level deployment directory is configured in the deployment service and its associated listener.

Under the “Services” tab for the region is a service used for deployment (you will see “Deployer” in the Service Namespace column). Click “Edit” for that service. You will be brought to a page which contains a box entitled “Configuration Information” (you will need to scroll down to see it). You should see the following in that box:

[MF client]

scheme=http

URL=/cgi/mfdeploy.exe/uploads

accept=application/x-zip-compressed

[destination]

listener=Web Services and J2EE

If you look at its available listeners (scroll up), you'll see it's associated with an accepting listener named “Web".

Edit that Web listener, and you'll find its configuration contains:

[virtual paths]

cgi=<ES>/bin

uploads=<ES>/deploy

<default>=/dev/null

docs=<ES>/help

The key information here is the URL setting in the [MF client] section of the service configuration, and the uploads setting in the [virtual paths] section of the listener configuration.

When you select the Deployer deployment service, MFCC forms the Request-URI for the HTTP request to the deployment service by taking the value of the URL setting and appending the CAR filename to it. So your deployment request will specify /cgi/mfdeploy.exe/uploads/something.car. /cgi/mfdeploy.exe is the virtual path to the deployer program. /uploads/something.car is CGI path-info; it's passed to the deployer program, after virtual path mapping is applied.

The /uploads part of the path-info is mapped to the value of the uploads virtual path, which is <ES>/deploy; and <ES> is expanded into the product installation directory.

So to change the top-level deployment directory, the easiest thing to do is to change the value of uploads in the listener configuration. (You could also create a new virtual path there, and then edit the deployment service definition, or create a new deployment listener and/or service, etc.)

Please note that the deployment directory must contain a .mfdeploy file.

See the topic "Deployment Services and Listeners" in the product documentation for more information.