Running the Container Demonstration for the Enterprise Developer Base Image

The container demonstration to create the Enterprise Developer base image includes a batch file (bld.bat) to make the process of running the demonstration as easy as possible. This topic lists and describes the parameters that you can specify when running bld.bat.

For users of Enterprise Developer for Eclipse (Windows):

When using bld.bat to create a base image for Enterprise Developer you need to ensure that the relevant installation files and licenses are available in the same folder as bld.bat. These are:

The installable executable file for Enterprise Developer Build Tools for Windows. This is edbt_90.exe and is supplied in the container demonstration for the Enterprise Developer Build Tools for Windows base image.
The appropriate license (.mflic or .xml) file for Enterprise Developer Build Tools for Windows.
If you will be including Java support in the image, the relevant executable file to perform the installation of the JDK. You can get this file from your chosen JDK provider.

The command to execute the batch file to run the container demonstration for the Enterprise Developer base image is as follows:

bld.bat { IacceptEULA [dryrun] [hotfix <patch-update-installer-exe>] [openjdk32] [nojava] [verbose] [install-location] | rmi | settings }

where the parameters are:

IacceptEULA: Indicates that you accept the Micro Focus End User License Agreement (EULA).
You must specify IacceptEULA to create a base image containing Enterprise Developer.
dryrun: Indicates that you do not want bld.bat to run any Docker commands. Use dryrun with the verbose parameter to display the Docker commands without running them.
hotfix <patch-update-installer-exe>: Specifies the executable installer for the patch update, which is included in product download .zip file. Use this option to build the Enterprise Developer base image demontration that is based off of a patch update install.
install-location: Specifies the name of the folder in the image filesystem into which Enterprise Developer will be installed. If specified, this must be the last parameter.
openjdk32: Indicates that you want to include the 32-bit version of AdoptOpenJDK OpenJDK in your base product images or want to use the _x86 suffix tags to build your Ant-based projects. Specifying openjdk32 downloads and configures the AdoptOpenJDK 1.8 x86 version into your base images and configures the 32-bit tags (with a suffix of _x86) ready for use.
nojava: Indicates that you do not want Java to be installed in the base image. By default, the base image includes Java support as provided by the AdoptOpenJDK OpenJDK. You might want to use this if your system already includes a number of different versions of Java and you don't want to introduce another version unnecessarily.
rmi: Indicates that you want to remove any previously-created Enterprise Developer base images. Specifying rmi results in the execution of a number of docker rmi --force commands to remove all Enterprise Developer base images.
settings: Causes the settings that will be used for various properties of the image to be displayed on-screen. Properties that are displayed include the names of the installable file and the license file for Enterprise Developer, the details to be used for the Enterprise Server admin user, and the details to be used for the login image. Specifying settings does not cause an image to be created.
verbose: Causes Docker commands to be displayed on-screen as they are executed.

For users of Enterprise Developer for Eclipse (UNIX), or Enterprise Developer UNIX Components: or Enterprise Developer for Eclipse:

Note: When using bld.sh to create a base image for Enterprise Developer you need to ensure that the relevant installation files and licenses are available in the same folder as bld.sh. These are:

The installable executable for Enterprise Developer. This is setup_entdev_for_docker_9.0_platform and is supplied in the Docker demonstration for the Enterprise Developer base image.
The appropriate license (.mflic or .xml) for Enterprise Developer.
If you will be including Java support in the image, the relevant executable file to perform the installation of the JDK. You can get this file from your chosen JDK provider.

The command to execute the shell script to run the container demonstration for the Enterprise Developer base image is as follows:

./bld.sh IacceptEULA  
         [dryrun]
         [esadmgid=admin-gid]
         [esadmuid=admin-uid]
         [esadminuser=admin-id]
         [hotfix=tar-file-name]
         [nojava | (java | oraclejava) [javaversion=java-version]]
         [login|nologin] 
         [logingid=login-gid]
         [loginid=login-id]
         [logingname=login-gname]
         [loginname=login-name]
         [notools]
         [odbc|odbc-dev]
         [package]
         [rmi]
         [settings]
         [verbose]

where the parameters are:

IacceptEULA

Indicates that you accept the Micro Focus End User License Agreement (EULA).

You must specify IacceptEULA to create a base image containing Enterprise Developer.

dryrun

Indicates that you do not want bld.sh to run any Docker or podman commands. Use dryrun with the verbose parameter to display the Docker or podman commands without running them.

esadminuser=admin-id

Specifies the ID to be used for the Enterprise Server admin user.

esadmgid=admin-gid

Specifies the group ID to use for the Enterprise Server admin user.

esadmuid=admin-uid

Specifies the user ID to use for the Enterprise Server admin user.

hotfix=tar-file-name

This option is only for installing a Patch Update version. Specify the name of the installable executable .tar file as mentioned above, without the extension. For example: hotfix=setup_visualcobol_devhub_for_docker_8.0_patchupdate03_312109_ platform_x64.

java

Indicates that you want the image to include Java support provided by Adoptium's OpenJDK. Use the javaversion parameter to specify the version of Java that you want support for.

javaversion=java-version

When specified in conjunction with the oraclejava parameter, java-version specifies the Java version you want support for, which can be 8 or 9; otherwise, when specified in conjunction with the java parameter, java-version can be 8, 10-18.

login

Indicates that you want to create a login image. Using this option results in image that you can use to log in to (using any details specified by the logingid, loginid, logingname and loginname parameters). Once logged in to this image you can execute shell or Enterprise Developer commands.

This option is useful if you are not adding any application files to a base image but want to be able to use Enterprise Developer commands from it.

When you specify login the tag of the image created is suffixed with "_login".

logingid=login-gid

Specifies the group ID to use for the user specified by the loginid parameter.

loginid=login-id

Specifies the user ID to use for the login image.

logingname=login-gname

Specifies the group name to use for the user specified by the loginid parameter.

loginname=login-name

Specifies the user name to use for the user specified by the loginid parameter.

nojava

Indicates that you do not want Java to be installed in the base image. You might want to use this parameter if your system already includes a number of different versions of Java and you don't want to introduce another version unnecessarily.

nologin

Indicates that you do not want to create a login image. You would typically want to use this option when creating an image that contains an application rather than just a base image for Enterprise Developer. This is the default.

notools

Indicates that you do not want the image to contain the IP tools (such as ping and netcat) that are included in the image by default. Use this option if you do not need the tools and want to minimize the size of the image.

odbc|odbc-dev

Specifies that the odbc run-time library or the odbc developer tools library is installed. (UNIX/Linux platforms only.)

oraclejava

Indicates that you want the image to include Java support provided by the Oracle JDK. Use the javaversion parameter to specify the version of Java that you want support for.

package

Indicates that you want to rebuild the COBOL application in this image.

rmi

Indicates that you want to remove any previously-created Enterprise Developer base images. Specifying rmi results in the execution of a number of docker rmi --force or podman rmi --force commands to remove all Enterprise Developer base images.

settings

Causes the settings that will be used for various properties of the image to be displayed on-screen. Properties that are displayed include the names of the installable file and the license file for Enterprise Developer, the details to be used for the Enterprise Server admin user, and the details to be used for the login image. Specifying settings does not cause an image to be created.

verbose

Causes Docker or podman commands to be displayed on-screen as they are executed.