Skip to main content

Using Net Express 5.1 to deploy a Cobol web service to a remote Enterprise Server.  The Settings dialog for the service does not list the remote Enterprise Server as a target for deployment.  It used to do so before the remote Enterprise Server was rehosted to a different server on the same network. The remote Enterprise Server is definitely up and running.  Is there a setting or configuration parameter I need to update so Net Express can find the remote Enterprise Server?

Using Net Express 5.1 to deploy a Cobol web service to a remote Enterprise Server.  The Settings dialog for the service does not list the remote Enterprise Server as a target for deployment.  It used to do so before the remote Enterprise Server was rehosted to a different server on the same network. The remote Enterprise Server is definitely up and running.  Is there a setting or configuration parameter I need to update so Net Express can find the remote Enterprise Server?

I believe that you need to edit your mf-client.dat file to add the server name.

To deploy to a remote enterprise server

On the COBOL development system machine, open the file mf-client.dat in a text editor.
This file is in the base\\bin of your COBOL development system installation.

Add the following line at the end:

mrpi://myESmachine

Where myESmachine is the name of the remote machine where your enterprise server runs.

You can keep any existing lines that point to other machines running an enterprise server.
You do not need to specify the port number. The default port number 86 is used.

Save the file.

Restart your COBOL development system if it is already running, so that the remote enterprise servers are available locally.

Deploy the service interface using the Deploy

Using Net Express 5.1 to deploy a Cobol web service to a remote Enterprise Server.  The Settings dialog for the service does not list the remote Enterprise Server as a target for deployment.  It used to do so before the remote Enterprise Server was rehosted to a different server on the same network. The remote Enterprise Server is definitely up and running.  Is there a setting or configuration parameter I need to update so Net Express can find the remote Enterprise Server?

Chris' answer, which comes from the product documentation, isn't quite correct. (I just noticed this now - I'll have to raise an RPI against the documentation.)

The "mrpi://hostname" line being added to mf-client.dat must be added to the [directories] section of the file. I don't remember exactly what's in mf-client.dat in the 5.1 product line, but in more recent products, there are other sections after [directories], so adding the line "at the end" will most definitely not work.

So, for example, if the hostname of your remote server is "esserver", then your mf-client.dat file should begin with:

[directories]
mrpi://localhost
mrpi://esserver

Using Net Express 5.1 to deploy a Cobol web service to a remote Enterprise Server.  The Settings dialog for the service does not list the remote Enterprise Server as a target for deployment.  It used to do so before the remote Enterprise Server was rehosted to a different server on the same network. The remote Enterprise Server is definitely up and running.  Is there a setting or configuration parameter I need to update so Net Express can find the remote Enterprise Server?

Actually, I just noticed that it's correct in the latest product documentation - see for example:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.studee60win/HHIMTHDPOY14.html

It looks like it was wrong in the 5.1 documentation and the old (offline) 6.0 documentation.

Using Net Express 5.1 to deploy a Cobol web service to a remote Enterprise Server.  The Settings dialog for the service does not list the remote Enterprise Server as a target for deployment.  It used to do so before the remote Enterprise Server was rehosted to a different server on the same network. The remote Enterprise Server is definitely up and running.  Is there a setting or configuration parameter I need to update so Net Express can find the remote Enterprise Server?

Thanks, Chris.  That fixed the problem.  "myESmachine" was defined using an IP address not a hostname.  When the server was relocated its IP address changed.  I i update mfclient.dat as you suggested, and all is working fine now.

Terms & ConditionsAccessibility statement