Installing MDOpen Web
Version 8.6
Published June 17, 2025
Overview & Architecture
MDOpen Web is a browser-based installation of MDOpen for VSCODE.
It is installed and runs natively as a web application from an IBM i HTTP server instance.
MDOpenweb uses the same MDCMS REST APi's as MDOpen-RDi and MDOpen-VSCODE-Desktop, to retrieve the content.
MDOpenweb Architecture
Pre-Requisites
- MDCMS Rest API Server installed and configured with SSL/TLS/HTTPS access.
- Available TCP port numbers for MDOpenweb HTTP server instance. Consult with your Operations/Infrastructure Administrator
- IBM i Digital Certificate Manager server application name
- MDCMS Instance Suffix
- V7R2M0 IBM i OS or later
- *SECADM Authority
Additional Parameters Required for MDOPENWEB Servers:
| Parameter | Description |
|---|---|
| MDCMS Environment | The instance of MDCMS on the partition. If it is the default instance (libraries = MDCMS, MDREP, MDSEC, and MDXREF) then leave this value blank. Otherwise, set the value to the suffix of the library names |
| MDCMS API Server Host | The host name or IP address of the partition where the MDCMS API server is running. This cannot be localhost, since the connection is established from the user's browser and not from the MDOpen for Web server. The MDCMS API server must have https enabled either directly or via a proxy server. |
| MDCMS API SSL Port | The SSL-Enabled port number that the MDCMS API Server is listening on. |
SSL/HTTPS Mandatory
Communication to the MDOpenweb HTTP server and to the MDChange REST API servers MUST be using HTTPS scheme
MDOPENWEB Server Installation Process
Note
The MDOPENWEB configuration screen requires the input of the REST API server details added previous. Therefore ensure the REST API server is installed and running before starting the MDOPENWEB installation process.
All MDChange HTTP Servers are configured from the same screens. MDCMS RESTAPI Server must be configured and running before installing MDOPENWEB servers.
Navigate to MDCMS HTTP Servers Screen screen using:
- Command MDCMS within a 5250 session
- Option 1 - MDCMS Setup Menu
- Option 10 - Interface Settings
- Option 9 - HTTP Servers - lists available REST API
MDCHTTP T86 Dev/Test 16.06.25
SCRN1 MD HTTP Servers 16:03:47
Type options, press Enter.
2=Edit 3=Copy 4=Delete 5=View D=Default E=End I=IFS S=Start
Non-SSL SSL
Instance Type Status Port Port JobD Name JobD Lib Dft
MDCMST86 API Running 2586 MDAPIT86 QGPL Y
Info
More Details about MDCMS HTTP Servers Screen
From the MDCMS HTTP Servers Screen, select command key F6 to add a new server
MDCHTTP T86 Dev/Test 16.06.25
SCRN2 Add an MD HTTP Server 15:54:12
Server Type: 1=MDCMS API Server (Apache)
3=MDOpen for Web Server (Apache)
NOTE: An MDCMS API Server is a pre-requisite for using MDOpen for RDi,
MDOpen for VS Code or MDOpen for Web.
...
Enter=Continue F12=Cancel
Use option 3 to create a new MDOPENWB server instance, and press enter.
MDCHTTP T86 Dev/Test 17.06.25
SCRN3 Create MDOpen for Web Server 19:24:50
Server Name . . . . . . MDOPWT86
Non-SSL Port Number . .
SSL Port Number . . . .
DCM Application . . . .
MDCMS Environment . . . T86
MDCMS API Server Host . dev.mdcms.ch
MDCMS API SSL Port . . 443
Server URL
https://dev.mdcms.ch
Enter=Confirm F12=Cancel F12=Sys Command
| Parameter | Description |
|---|---|
| Server Name | The name of the Server to create. The server will be replaced if it already exists. Normally, only one server should be active for a given instance and partition of MDCMS. When created, the server configuration will be placed in IFS folder /www/<server name> |
| Non-SSL Port Number | The port number that the server should listen to for incoming insecure http requests. *NONE - an insecure port should not be configured. Port number - a number up to 5 digits that isn't used by any other server on the partition. |
| SSL Port Number | The port number that the server should listen to for incoming https requests. *NONE - an SSL port should not be configured. Port number - a number up to 5 digits that isn't used by any other server on the partition. |
| DCM Application | The name of an Application in the *SYSTEM certificate store that is assigned to the preferred SSL certificate. This is only necessary when configuring an SSL port. creating a DCM Application |
| MDCMS Environment | The Instance name that MDCMS runs under |
| MDCMS API Server Host | The host name or IP address that exposes the MDCMS REST APIs. See Managing HTTP Servers above for details on the REST API server |
| MDCMS API SSL Port | The SSL port number used to host the MDCMS REST API server. Thsi can be directly configured in the MDCMS REST API server instance, or behind a reverse-proxy server. |
| Server URL | The server URL is the address of the partition, including the transport method: http or https. Don't include the context path in the endpoint. Example: https://devbox.mycompany.com When a REST request is sent to the endpoint, it will then be followed by the name of the mdcms instance (usually mdcms) and then the resource name of the API to be invoked. Example: to get a list of all applications defined in MDCMS: https://devbox.mycompany.com/mdcms/applications |
When Enter is pressed, the server is created and automatically started. The MD HTTP Servers screen will update and show the REST API server added to the list:
MDCHTTP T86 Dev/Test 17.06.25
SCRN1 MD HTTP Servers 19:41:18
Type options, press Enter.
2=Edit 3=Copy 4=Delete 5=View D=Default E=End I=IFS S=Start
Non-SSL SSL
Instance Type Status Port Port JobD Name JobD Lib Dft
MDCMST86 API Running 2586 MDAPIT86 QGPL Y
MDOPWT86 MDOPENWEB Running 2571 Y
Verify MDOpenweb Server is Running
To check if the server is running, in the web browser type in :
https://your_hostname:ssl_port
You should be presented with the login screen for MDOpenweb
Installation Logs
The installation log is found in one of two places:
/mdcms/temp/<server_instance_name>_installation_audit_<date>_<time>.log
or
/www/<server_instance_name>/logs/<server_instance_name>_installation_audit_<date>_<time>.log
Info
Prefix the paths above with /<IASP name> as applicable