- HTTP 403 page
- ESMAC contains defence mechanism against cross-site request forgery attacks. As a result, a 403 page is displayed in the browser
if an incorrect authentication token is sent in a request to ESMAC that performs a protected operation, such as submitting
a job or updating a resource definition.
If you receive a 403 page when using ESMAC, try clearing your session cookies as there might be a stale cookie value left
behind which is triggering the page. If the page continues to appear, contact
OpenText Support for Micro Focus Products for assistance.
- Using more than one region in the same browser session
- ESMAC contains defence mechanism against cross-site request forgery attacks. As a result of this, it is currently not possible
to log in into two different regions within the same browser session. This is because cookies are used as part of the authentication
process, and each region needs its own version of the authentication cookies to keep the ESMAC session valid.
You can work around this issue in one of the following ways:
- Open each new ESMAC session in a separate private or incognito browser window for each region you want to access concurrently
alongside any other running regions.
- Alternatively, use ESCWA to manage your regions.
- Upgrading Enterprise Server
-
If you upgraded from a version of Micro Focus Server and have retained any enterprise servers that have a Web Services listener,
you will receive an error when you deploy informing you that the listener cannot be found. To fix this, change the listener
name before deploying using one of the following methods:
- From Enterprise Server Administration, change the listener name from
Web Services to
Web Services and J2EE.
- Edit your deployment service (usually named
Deployer) and add the following lines to the Configuration Information area:
[destination] listener=Web Services
- If your deployment service doesn't have the listener name specified, edit the
base\deploy\.mfdeploy file changing the
Web Services listener name to
Web Services and J2EE .
- Dynamic Debugging with Enterprise Server
-
If dynamic debugging is not enabled for the enterprise server on which you are running an application, you receive an alert
when you try to debug. You need to enable dynamic debugging for the server by checking
Allow Dynamic Debugging on the
Edit page of Enterprise Server Administration and restarting the server or by checking
Dynamic Debug on the
ESMAC >
Control page which will enable debugging until the server is stopped.
- Debugging Assembler modules with Enterprise Server
- The MFASM debugger is unable to open a window for debugging on any
enterprise server region started via ESWCA, as Microsoft has permanently disabled access to the user desktop from any application started in the background
and owned by "SYSTEM".
- Enterprise Server Administration Web page
-
If the buttons on the Enterprise Server Administration Web page don't work, you need to enable Active Scripting or Javascript
in your browser.
-541326
- Active Content Blocked
-
If the Web Browser tells you it's blocking active content, when you view the Help, you need to allow active content.
- Viewing the Help
-
You can view the
COBOL Server Help in a separate browser window while you are using the Enterprise Server Administration Web interface, by clicking
Contents in the menu at the left-hand side of the page. For this link to work, you must have the following in place:
- An enterprise server that has a Web listener with the following entry in the
[virtual paths] section:
docs=<ES>/help
- The enterprise server must be started
- ESDEMO Configuration
-
The default enterprise server, ESDEMO, may not have the correct configuration information entry for its Web listener. If you
encounter problems accessing the Help while you are using ESDEMO, you must correct the entry using the Edit Listener page.
Note that references to this configuration entry in the context help and the Enterprise Server Configuration and Administration
Guide are no longer correct and you must use the entry as specified above.
When you create a new enterprise server, a Web listener with the required configuration information entry is automatically
created.
- Remote File Access
- Remote File Access in this release might not operate correctly when uploading files if the client uses all three of: a multipart
content-type (such as "multipart/form-data"), the "chunked" transfer-encoding, and the "gzip" transfer encoding. This issue
can be avoided by not using gzip compression when using a multipart content-type.
- Run Time
- When running Enterprise Server applications on HP Itanium in 32-bit mode, you could receive an error such as "CASCD1057S JES
Initiator for Server ... abended by signal 00004". In this case, set the environment value COBMAINSTACK to a value greater
than 500000 to increase the default stack size.