Home
%3CLINGO-SUB%20id%3D%22lingo-sub-358622%22%20slang%3D%22en-US%22%3ERunning%20Micro%20Focus%20Enterprise%20Server%204.0%20in%20a%20Docker%20Container%20in%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358622%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3EAuthored%20by%20Steve%20Read%20from%20AzureCAT%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20few%20months%20ago%20I%20posted%20a%20blog%20about%20how%20to%20setup%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzureCAT%2FSet-up-Micro-Focus-Enterprise-Server-4-0-and-Enterprise%2Fba-p%2F306502%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EMicro%20Focus%20Enterprise%20Server%204.0%20and%20Enterprise%20Developer%204.0%20in%20Azure%3C%2FA%3E.%26nbsp%3BThere%20was%20a%20follow%20up%20to%20that%20blog%20outlining%20how%20to%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzureCAT%2FSet-up-Micro-Focus-CICS-BankDemo-for-Micro-Focus-Enterprise%2Fba-p%2F306599%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Econfigure%20and%20deploy%20the%20BankDemo%3C%2FA%3E%20application%20that%20comes%20with%20Enterprise%20Developer.%20I'd%20like%20to%20continue%20in%20this%20Micro%20Focus%20vein%20by%20outlining%20how%20to%20run%20Micro%20Focus%20Enterprise%20Server%20in%20a%20Docker%20Container.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENew%20to%20Micro%20Focus%20Enterprise%20Server%204.0%20is%20the%20ability%20to%20run%20in%20a%20Docker%20container.%26nbsp%3BThe%20%3CA%20href%3D%22https%3A%2F%2Fwww.microfocus.com%2Fdocumentation%2Fenterprise-developer%2Fed40%2FES-WIN%2FGUID-F5BDACC7-6F0E-4EBB-9F62-E0046D8CCF1B.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ebenefits%20of%20running%20Enterprise%20Server%20in%20Docker%3C%2FA%3E%20are%20centered%20around%20portability%2C%20performance%2C%20agility%20and%20isolation.%26nbsp%3BFor%20instance%2C%20a%20Docker%20image%20can%20be%20exported%20from%20one%20Windows%20VM%20to%20another%20or%20from%20another%20repository%2C%20and%20imported%20into%20another%20Windows%20server%20(assuming%20Docker%20support%20is%20installed%20there).%26nbsp%3BIt%20can%20then%20be%20run%20in%20the%20same%20way%20without%20having%20to%20install%20Enterprise%20Server%20because%20it%20is%20a%20part%20of%20the%20image%20(licensing%20considerations%20do%20still%20apply).%26nbsp%3BFor%20the%20purposes%20of%20this%20blog%2C%20I%20have%20decided%20to%20show%20how%20to%20set%20this%20up%20using%20the%20%3CSTRONG%3EWindows%202016%20Datacenter%20with%20Containers%3C%2FSTRONG%3E%20VM%20which%20is%20available%20from%20the%20Azure%20Marketplace.%20The%20nice%20thing%20about%20this%20offering%20is%20that%20%3CSTRONG%3EDocker%2018.09.0%3C%2FSTRONG%3E%20is%20already%20preinstalled%20and%20ready%20to%20go.%26nbsp%3BAll%20we%20will%20need%20to%20do%20is%20deploy%20the%20container%2C%20run%20it%20and%20then%20connect%20to%20it%20with%20a%203270%20emulator.%26nbsp%3BAt%20the%20end%20of%20this%20post%2C%20you%20will%20effectively%20be%20running%20a%20Mainframe%20application%20in%20a%20container.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet's%20get%20started.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EFirst%20a%20note%20about%20the%20media%20and%20licensing%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EIn%20order%20to%20complete%20this%20walk%20through%2C%20you%20will%20need%20to%20have%20access%20to%20the%20Micro%20Focus%20media.%26nbsp%3BThis%20is%20available%20for%20Micro%20Focus%20customers%20and%20potential%20customers%20via%20a%20trial.%26nbsp%3BIf%20you%20have%20access%20to%20Enterprise%20Server%204.0%20or%20Enterprise%20Developer%204.0%2C%20you%20should%20have%20access%20to%20the%20accompanying%20Docker%20Support%20files.%26nbsp%3BIf%20you%20do%20not%20have%20access%2C%20you%20can%20go%20%3CA%20href%3D%22https%3A%2F%2Fwww.microfocus.com%2Fproducts%2Fenterprise-suite%2Fenterprise-server%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20to%20get%20the%20process%20started.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20two%20sets%20of%20demonstrations%20available%3A%20one%20set%20for%20%3CSTRONG%3EEnterprise%20Server%3C%2FSTRONG%3E%20and%20another%20for%20%3CSTRONG%3EEnterprise%20Developer%3C%2FSTRONG%3E.%26nbsp%3BWithin%20these%20two%20sets%2C%20there%20are%20demonstrations%20for%20Windows%20based%20platforms%20and%20SUSE%20Linux.%20For%20this%20blog%20you%20are%20going%20to%20walk%20through%20the%20Windows%20CICS%20%3CEM%3Eacctdemo%3C%2FEM%3E%20demonstration%20for%20Enterprise%20Server.%20The%20accompanying%20files%20are%20in%20a%20zip%20file%20named%3A%26nbsp%3B%3CSTRONG%3Eent_server_dockerfiles_4.0_windows.zip.%26nbsp%3B%3C%2FSTRONG%3EThere%20is%20an%20accompanying%20licensing%20file%20with%20a%20name%20similiar%20to%3CSTRONG%3E%20ES-Docker-Prod-XXXXXXXX.mflic%3C%2FSTRONG%3E%20that%20will%20be%20necessary%20in%20order%20to%20build%20the%20Docker%20images.%26nbsp%3BOnce%20you%20have%20secured%20the%20media%20and%20the%20appropriate%20licensing%20file%2C%20you%20can%20begin.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CSTRONG%3ECreate%20the%20VM%20-%20%3C%2FSTRONG%3EThe%20first%20thing%20we%20will%20need%20to%20do%20is%20create%20the%20VM%20in%20Azure%20via%20the%20Azure%20Portal.%26nbsp%3BAs%20I%20mentioned%20before%2C%20we%20are%20going%20to%20use%20the%20Windows%20Server%202016%20Datacenter%20-%20with%20Container%20VM%20which%20is%20available%20in%20the%20Azure%20Marketplace.%26nbsp%3BIf%20you%20select%20Create%20Resource%20from%20the%20top%20left%20of%20the%20Portal%20and%20then%20filter%20by%20%22Docker%22%20and%20then%20select%20Windows%20Server%202016%2C%20you%20can%20select%20the%20VM.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20896px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84757iC2C8BDDECD9C9EDE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_1.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3ENext%2C%20you%20will%20need%20to%20configure%20the%20properties%20for%20the%20VM.%26nbsp%3BThe%20Windows%20Server%20with%20Containers%20VM%20is%20only%20available%20in%20certain%20VM%20sizes.%20I%20chose%20a%20%3CSTRONG%3EStandard%20DS2_v2%3C%2FSTRONG%3E%20with%202%20vcpus%20and%207GB%20of%20memory.%26nbsp%3BYou%20will%20also%20need%20to%20select%20the%20%3CSTRONG%3ERegion%3C%2FSTRONG%3E%20and%20%3CSTRONG%3EResource%20Group%3C%2FSTRONG%3E%20you%20would%20like%20to%20deploy%20to.%20We%20do%20not%20need%20any%20%3CSTRONG%3EAvailability%20options%3C%2FSTRONG%3E%20for%20this%20walk%20through.%26nbsp%3B%20You%20will%20need%20to%20input%20the%20Username%20you%20would%20like%20to%20use%20for%20the%20%3CSTRONG%3EAdministrator%20Account%3C%2FSTRONG%3E%20as%20well%20as%20the%20%3CSTRONG%3EPassword%3C%2FSTRONG%3E.%26nbsp%3BFinally%20make%20sure%20%3CSTRONG%3Eport%203389%20RDP%3C%2FSTRONG%3E%20is%20open.%26nbsp%3BThis%20is%20the%20only%20port%20you%20need%20to%20publicly%20expose.%26nbsp%3BYou%20will%20need%20it%20to%20log%20into%20the%20VM.%26nbsp%3B%20After%20this%20you%20can%20accept%20all%20of%20the%20default%20values%20and%20click%20Review%2B%20Create.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20825px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84758iEF9928143A585D8F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_2.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3EThe%20deployment%20could%20take%20a%20couple%20of%20minutes.%26nbsp%3BWhen%20it%20is%20complete%20you%20will%20be%20presented%20with%20a%20message%20stating%20your%20VM%20has%20been%20created%20with%20a%20link%20to%3CSTRONG%3E%20Go%20to%20Resource%3C%2FSTRONG%3E.%26nbsp%3BClick%20this%20and%20you%20will%20be%20taken%20to%20the%20Overview%20blade%20for%20your%20VM.%26nbsp%3BIn%20the%20right%20pane%2C%20you%20will%20see%20a%20%3CSTRONG%3EConnect%3C%2FSTRONG%3E%20button.%26nbsp%3BClick%20this%20and%20you%20will%20see%20the%20%3CSTRONG%3EConnect%20to%20virtual%20machine%3C%2FSTRONG%3E%20dialog%20pop%20up%20on%20the%20right.%26nbsp%3BClick%20on%20the%20%3CSTRONG%3EDownload%20RDP%20File%3C%2FSTRONG%3E%20button.%26nbsp%3BThis%20will%20download%20the%20RDP%20file%20that%20will%20allow%20you%20to%20attach%20to%20the%20VM.%26nbsp%3BAfter%20the%20file%20has%20finished%20downloading%2C%20open%20it%20and%20type%20in%20the%20Username%20and%20Password%20you%20created%20for%20the%20VM.%26nbsp%3BMake%20sure%20you%20are%20not%20using%20your%20corporate%20credentials%20to%20log%20on%20since%20the%20RDP%20client%20will%20assume%20you%20may%20want%20to%20use%20these.%26nbsp%3BYou%20do%20not.%26nbsp%3BSelect%20%3CSTRONG%3EMore%20Choices%3C%2FSTRONG%3E%20and%20you%20will%20be%20able%20to%20select%20your%20VM%20credentials.%20After%20this%2C%20you%20will%20be%20logged%20into%20the%20VM.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CSTRONG%3E2.%20Create%20Sandbox%20Directory%20and%20Upload%20the%20zip%20File%3C%2FSTRONG%3E%20-%20Now%20that%20we%20have%20the%20machine%20running%20and%20attached%20via%20RDP%2C%20create%20a%20Sandbox%20Directory%20and%20upload%20the%26nbsp%3B%3CSTRONG%3Eent_server_dockerfiles_4.0_windows.zip%20%3C%2FSTRONG%3Eand%20the%20%3CSTRONG%3EES-Docker-Prod-XXXXXXXX.mflic%26nbsp%3B%3C%2FSTRONG%3Eto%20that%20directory.%26nbsp%3B%20Extract%20the%20zip%20file%20contents%20to%20the%26nbsp%3B%3CSTRONG%3Eent_server_dockerfiles_4.0_windows%3C%2FSTRONG%3E%26nbsp%3Bdirectory%20(the%20extract%20will%20create%20this%20for%20you).%20Inside%20this%20directory%2C%20you%20will%20have%20a%20README%20html%20and%20txt%20file%20(two%20versions%20of%20the%20same%20thing).%26nbsp%3BYou%20will%20also%20have%202%20directories%20%3CSTRONG%3EEnterpriseServer%3C%2FSTRONG%3E%20and%20%3CSTRONG%3EExamples%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CSTRONG%3EVERY%20IMPORTANT%3C%2FSTRONG%3E%20-%20Make%20sure%20you%20copy%20the%20licensing%20file%26nbsp%3B%3CSTRONG%3EES-Docker-Prod-XXXXXXXX.mflic%20%3C%2FSTRONG%3Eto%20the%20%3CSTRONG%3EC%3A%5CSandbox%5Cent_server_dockerfiles_4.0_windows%5CEnterpriseServer%3C%2FSTRONG%3E%20directory%20and%20the%26nbsp%3B%3CSTRONG%3EC%3A%5CSandbox%5Cent_server_dockerfiles_4.0_windows%5CExamples%5CCICS%3C%2FSTRONG%3E.%26nbsp%3BAs%20I%20mentioned%20before%2C%20these%20are%20necessary%20for%20the%20Docker%20build%20step%20to%20make%20sure%20the%20images%20are%20properly%20licensed.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CSTRONG%3E3.%20Check%20Docker%20Version%20and%20Create%20Base%20Image%20-%20Very%20Important%3A%26nbsp%3B%3C%2FSTRONG%3ECreating%20the%20appropriate%20Docker%20image%20you%20need%20to%20use%20is%20a%202%20step%20process.%26nbsp%3BFirst%20you%20will%20need%20to%20create%20the%20Enterprise%20Server%204.0%20Base%20image.%26nbsp%3BAfter%20this%20is%20complete%20you%20will%20create%20another%20image%20for%20the%20x64%20platform.%20You%20also%20have%20the%20option%20to%20create%20a%20x86%20(32%20bit)%20image%2C%20but%20since%20you%20are%20running%20this%20in%20Azure%2C%20you%20will%20need%20the%2064%20bit%20image.%26nbsp%3BIn%20order%20to%20do%20this%2C%20open%20a%20Command%20Prompt.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECheck%20that%20Docker%20is%20installed.%26nbsp%3BAt%20the%20command%20prompt%2C%20type%20%3CSTRONG%3Edocker%20version%3C%2FSTRONG%3E.%26nbsp%3BYou%20should%20see%20a%20return%20similar%20to%20the%20image%20below.%26nbsp%3BAt%20the%20time%20of%26nbsp%3B%20this%20post%2C%20the%20version%20is%2018.09.0.%26nbsp%3BThis%20lets%20us%20know%20that%20Docker%20is%20installed.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20842px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84759iC6176846F82D354B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_3.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_3.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENext%2C%20we%20will%20need%20to%20switch%20to%20the%26nbsp%3B%3CSTRONG%3EC%3A%5CSandbox%5Cent_server_dockerfiles_4.0_windows%5CEnterpriseServer%3C%2FSTRONG%3E%3CSTRONG%3E.%26nbsp%3B%20%3C%2FSTRONG%3E%3CUL%3E%0A%3CLI%3EType%20%3CSTRONG%3Ecd%5CSandbox%5Cent_server_dockerfiles_4.0_windows%5CEnterpriseServer%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3ENext%20type%20%3CSTRONG%3Ebld.bat%20IacceptEULA%3C%2FSTRONG%3E%20at%20the%20prompt.%26nbsp%3BThis%20will%20kick%20off%20the%20build%20process%20for%20the%20initial%20base%20image.%26nbsp%3BThis%20will%20take%20a%20few%20minutes%20to%20run.%26nbsp%3BWhen%20it%20is%20done%2C%20you%20will%20see%20a%20return%20like%20the%20following.%26nbsp%3BNotice%20the%20two%20images%20that%20have%20been%20created%20(one%20for%20x64%20and%20x86).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20838px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84760i134A25E925A6B6CA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_4.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_4.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENow%20we%20need%20to%20switch%20to%20the%20CICS%20example%20director%20and%20create%20the%20final%20image%20for%20the%20CICS%20demonstration.%3CUL%3E%0A%3CLI%3EType%20%3CSTRONG%3Ecd%5CSandbox%5Cent_server_dockerfiles_4.0_windows%5CExamples%5CCICS%3C%2FSTRONG%3E%20to%20switch%20to%20the%20CICS%20directory.%3C%2FLI%3E%0A%3CLI%3ENow%20you%20need%20to%20create%20the%20image.%26nbsp%3BType%20%3CSTRONG%3Ebld.bat%20x64.%26nbsp%3B%3C%2FSTRONG%3EAgain%2C%20this%20will%20run%20for%20a%20few%20minutes.%26nbsp%3BWhen%20it%20is%20done%2C%20you%20should%20see%20a%20message%20stating%20that%20the%20image%20was%20created.%3C%2FLI%3E%0A%3CLI%3ETo%20confirm%20this%2C%20type%20%3CSTRONG%3Edocker%20images%3C%2FSTRONG%3E.%26nbsp%3BYou%20will%20see%20a%20list%20of%20all%20of%20the%20Docker%20images%20installed%20on%20the%20VM.%20Make%20sure%20%3CSTRONG%3Emicrofocus%2Fes-acctdemo%3C%2FSTRONG%3E%20is%20one%20of%20them.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84761i88DE890C94375583%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_5.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_5.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENow%20lets%20run%20the%20image.%26nbsp%3BThis%20will%20launch%20Enterprise%20Server%204.0%20and%20the%20acctdemo%20application.%3CUL%3E%0A%3CLI%3EAt%20the%20command%20prompt%20type%26nbsp%3B%3CSTRONG%3Edocker%20run%20-p%2016002%3A86%2Ftcp%20-p%2016002%3A86%2Fudp%20-p%209040-9050%3A9040-9050%20-p%209000-9010%3A9000-9010%20-ti%20--network%3D%22nat%22%20--rm%20microfocus%2Fes-acctdemo%3Awin_4.0_x64.%26nbsp%3B%3C%2FSTRONG%3ENow%20the%20image%20is%20running%20and%20we%20can%20can%20attach%20to%20it%20via%20a%203270%20emulator%20via%20port%209040.%26nbsp%3BFor%20this%20walk%20though%20I%20used%20%3CA%20href%3D%22http%3A%2F%2Fx3270.bgp.nu%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ex3270%3C%2FA%3E%2C%20but%20you%20can%20use%20whichever%20one%20you%20prefer.%26nbsp%3BGo%20ahead%20and%20install%20the%20emulator.%3C%2FLI%3E%0A%3CLI%3ENext%20we%20will%20need%20to%20get%20the%20ip%20address%20of%20the%20acctdemo%20container.%26nbsp%3BDocker%20acts%20as%20a%20DHCP%20Server%20for%20the%20Containers%20is%20manages.%3CUL%3E%0A%3CLI%3EFirst%2C%20we%20need%20to%20get%20the%20ID%20of%20the%20running%20Container.%26nbsp%3BType%20%3CSTRONG%3EDocker%20ps%3C%2FSTRONG%3E%20at%20the%20command%20prompt%20and%20note%20the%20ID.%26nbsp%3BYou%20will%20need%20this%20to%20get%20the%20IP%20address%20for%20the%20acctdemo%20Container.%20In%20this%20example%20it%20is%20%3CSTRONG%3E22a0fe3159d0%3C%2FSTRONG%3E.%3C%2FLI%3E%0A%3CLI%3ETo%20get%20the%20ip%20address%20type%20%3CSTRONG%3Edocker%20inspect%2022a0fe3159d0%20--format%3D%22%7B%7Brange%20.NetworkSettings.Networks%7D%7D%7B%7B.IPAddress%7D%7D%7B%7Bend%7D%7D%22%3C%2FSTRONG%3E.%26nbsp%3BYou%20should%20be%20presented%20with%20the%20ip%20address%20for%20the%20acctdemo%20image%20like%20in%20the%20image%20below.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20979px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84762iE41451E145882093%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_6.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_6.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENow%20let's%20mount%20the%20image%20using%20the%20emulator.%26nbsp%3BConfigure%20the%20emulator%20to%20use%20the%20address%20of%20the%20acctdemo%20image%20and%20port%209040.%26nbsp%3BFor%20this%20walk%20though%20it%20would%20be%20172.19.202.52%3A9040.%26nbsp%3BYours%20will%20be%20similar.%20You%20should%20be%20presented%20by%20a%20CICS%20logon%20screen%20like%20the%20one%20below.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20559px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84763iE058DF68EB8A83B3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_7.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_7.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENow%20you%20need%20to%20logon%20to%20the%20CICS%20Region.%26nbsp%3BYou%20can%20do%20this%20by%20entering%20%3CSTRONG%3ESYSAD%3C%2FSTRONG%3E%20for%20the%20%3CSTRONG%3EUSERID%3C%2FSTRONG%3E%20and%20%3CSTRONG%3ESYSAD%3C%2FSTRONG%3E%20for%20the%20%3CSTRONG%3EPassword%3C%2FSTRONG%3E.%3C%2FLI%3E%0A%3CLI%3ENext%20you%20need%20to%20clear%20the%20screen.%26nbsp%3BYou%20can%20find%20this%20on%20the%20keymap%20of%20the%20emulator%20you%20are%20using.%26nbsp%3BFor%20x3270%20select%20the%20%3CSTRONG%3EKeymap%3C%2FSTRONG%3E%20menu%20option.%3C%2FLI%3E%0A%3CLI%3ETo%20launch%20the%20acctdemo%20application%20type%20%3CSTRONG%3EACCT%3C%2FSTRONG%3E.%26nbsp%3BYou%20should%20see%20the%20initial%20screen%20for%20the%20application.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20559px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84764iC5E95AF4E8A714CE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_8.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_8.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20type%20%3CSTRONG%3ED%3C%2FSTRONG%3E%20for%20the%20Request%20and%20%3CSTRONG%3E11111%3C%2FSTRONG%3E%20for%20the%3CSTRONG%3E%20ACCOUNT%3C%2FSTRONG%3E%2C%20you%20be%20taken%20to%20some%20fictional%20account%20information.%26nbsp%3BOther%20account%20numbers%20to%20try%20are%2022222%2C%2033333....%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20559px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84765i621815EEAED4FFF5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_9.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_9.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFinally%2C%20to%20administer%20the%20Enterprise%20Server%2C%20type%26nbsp%3B%3CSTRONG%3Estart%20http%3A172.19.202.52%3A86%3C%2FSTRONG%3E%20from%20a%20command%20prompt.%26nbsp%3BThis%20will%20bring%20up%20the%20Enterprise%20Server%20Administration%20console.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84766i6F56716FF7FBACB7%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22RunningMicroFocusEnterpriseServer_10.jpg%22%20title%3D%22RunningMicroFocusEnterpriseServer_10.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESummary%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ENow%20you%20are%20running%20and%20managing%20a%20CICS%20application%20in%20a%20Docker%20Container.%26nbsp%3BHopefully%20this%20was%20interesting.%26nbsp%3BIn%20the%20future%20we%20will%20explore%20leveraging%20Kubernetes%20in%20Azure%20(AKS)%20for%20orchestrating%20and%20managing%20the%20containers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-358622%22%20slang%3D%22en-US%22%3E%3CP%3ESteve%20Read%20continues%26nbsp%3Bhis%20Micro%20Focus%20series%20by%20outlining%20how%20to%20run%20Micro%20Focus%20Enterprise%20Server%20in%20a%20Docker%20Container.%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Microsoft

Authored by Steve Read from AzureCAT

 

A few months ago I posted a blog about how to set up Micro Focus Enterprise Server 4.0 and Enterprise Developer 4.0 in Azure. There was a follow up to that blog outlining how to configure and deploy the BankDemo application that comes with Enterprise Developer. I'd like to continue in this Micro Focus vein by outlining how to run Micro Focus Enterprise Server in a Docker Container.

 

New to Micro Focus Enterprise Server 4.0 is the ability to run in a Docker container. The benefits of running Enterprise Server in Docker are centered around portability, performance, agility and isolation. For instance, a Docker image can be exported from one Windows VM to another or from another repository, and imported into another Windows server (assuming Docker support is installed there). It can then be run in the same way without having to install Enterprise Server because it is a part of the image (licensing considerations do still apply). For the purposes of this blog, I have decided to show how to set this up using the Windows 2016 Datacenter with Containers VM which is available from the Azure Marketplace. The nice thing about this offering is that Docker 18.09.0 is already preinstalled and ready to go. All we will need to do is deploy the container, run it and then connect to it with a 3270 emulator. At the end of this post, you will effectively be running a Mainframe application in a container.

 

Let's get started.

 

First a note about the media and licensing

In order to complete this walk through, you will need to have access to the Micro Focus media. This is available for Micro Focus customers and potential customers via a trial. If you have access to Enterprise Server 4.0 or Enterprise Developer 4.0, you should have access to the accompanying Docker Support files. If you do not have access, you can go here to get the process started.

 

There are two sets of demonstrations available: one set for Enterprise Server and another for Enterprise Developer. Within these two sets, there are demonstrations for Windows based platforms and SUSE Linux. For this blog you are going to walk through the Windows CICS acctdemo demonstration for Enterprise Server. The accompanying files are in a zip file named: ent_server_dockerfiles_4.0_windows.zip. There is an accompanying licensing file with a name similiar to ES-Docker-Prod-XXXXXXXX.mflic that will be necessary in order to build the Docker images. Once you have secured the media and the appropriate licensing file, you can begin.

 

  1. Create the VM - The first thing we will need to do is create the VM in Azure via the Azure Portal. As I mentioned before, we are going to use the Windows Server 2016 Datacenter - with Container VM which is available in the Azure Marketplace. If you select Create Resource from the top left of the Portal and then filter by "Docker" and then select Windows Server 2016, you can select the VM.

RunningMicroFocusEnterpriseServer_1.jpg

 

Next, you will need to configure the properties for the VM. The Windows Server with Containers VM is only available in certain VM sizes. I chose a Standard DS2_v2 with 2 vcpus and 7GB of memory. You will also need to select the Region and Resource Group you would like to deploy to. We do not need any Availability options for this walk through.  You will need to input the Username you would like to use for the Administrator Account as well as the Password. Finally make sure port 3389 RDP is open. This is the only port you need to publicly expose. You will need it to log into the VM.  After this you can accept all of the default values and click Review+ Create.

 

RunningMicroFocusEnterpriseServer_2.jpg

 

The deployment could take a couple of minutes. When it is complete you will be presented with a message stating your VM has been created with a link to Go to Resource. Click this and you will be taken to the Overview blade for your VM. In the right pane, you will see a Connect button. Click this and you will see the Connect to virtual machine dialog pop up on the right. Click on the Download RDP File button. This will download the RDP file that will allow you to attach to the VM. After the file has finished downloading, open it and type in the Username and Password you created for the VM. Make sure you are not using your corporate credentials to log on since the RDP client will assume you may want to use these. You do not. Select More Choices and you will be able to select your VM credentials. After this, you will be logged into the VM.

2. Create Sandbox Directory and Upload the zip File - Now that we have the machine running and attached via RDP, create a Sandbox Directory and upload the ent_server_dockerfiles_4.0_windows.zip and the ES-Docker-Prod-XXXXXXXX.mflic to that directory.  Extract the zip file contents to the ent_server_dockerfiles_4.0_windows directory (the extract will create this for you). Inside this directory, you will have a README html and txt file (two versions of the same thing). You will also have 2 directories EnterpriseServer and Examples.

VERY IMPORTANT - Make sure you copy the licensing file ES-Docker-Prod-XXXXXXXX.mflic to the C:\Sandbox\ent_server_dockerfiles_4.0_windows\EnterpriseServer directory and the C:\Sandbox\ent_server_dockerfiles_4.0_windows\Examples\CICS. As I mentioned before, these are necessary for the Docker build step to make sure the images are properly licensed.

3. Check Docker Version and Create Base Image - Very Important: Creating the appropriate Docker image you need to use is a 2 step process. First you will need to create the Enterprise Server 4.0 Base image. After this is complete you will create another image for the x64 platform. You also have the option to create a x86 (32 bit) image, but since you are running this in Azure, you will need the 64 bit image. In order to do this, open a Command Prompt.

  • Check that Docker is installed. At the command prompt, type docker version. You should see a return similar to the image below. At the time of  this post, the version is 18.09.0. This lets us know that Docker is installed.

RunningMicroFocusEnterpriseServer_3.jpg

  • Next, we will need to switch to the C:\Sandbox\ent_server_dockerfiles_4.0_windows\EnterpriseServer
    • Type cd\Sandbox\ent_server_dockerfiles_4.0_windows\EnterpriseServer
    • Next type bld.bat IacceptEULA at the prompt. This will kick off the build process for the initial base image. This will take a few minutes to run. When it is done, you will see a return like the following. Notice the two images that have been created (one for x64 and x86).

RunningMicroFocusEnterpriseServer_4.jpg

 

  • Now we need to switch to the CICS example director and create the final image for the CICS demonstration.
    • Type cd\Sandbox\ent_server_dockerfiles_4.0_windows\Examples\CICS to switch to the CICS directory.
    • Now you need to create the image. Type bld.bat x64. Again, this will run for a few minutes. When it is done, you should see a message stating that the image was created.
    • To confirm this, type docker images. You will see a list of all of the Docker images installed on the VM. Make sure microfocus/es-acctdemo is one of them.

RunningMicroFocusEnterpriseServer_5.jpg

  • Now lets run the image. This will launch Enterprise Server 4.0 and the acctdemo application.
    • At the command prompt type docker run -p 16002:86/tcp -p 16002:86/udp -p 9040-9050:9040-9050 -p 9000-9010:9000-9010 -ti --network="nat" --rm microfocus/es-acctdemo:win_4.0_x64. Now the image is running and we can can attach to it via a 3270 emulator via port 9040. For this walk though I used x3270, but you can use whichever one you prefer. Go ahead and install the emulator.
    • Next we will need to get the ip address of the acctdemo container. Docker acts as a DHCP Server for the Containers is manages.
      • First, we need to get the ID of the running Container. Type Docker ps at the command prompt and note the ID. You will need this to get the IP address for the acctdemo Container. In this example it is 22a0fe3159d0.
      • To get the ip address type docker inspect 22a0fe3159d0 --format="{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}". You should be presented with the ip address for the acctdemo image like in the image below.

RunningMicroFocusEnterpriseServer_6.jpg

  • Now let's mount the image using the emulator. Configure the emulator to use the address of the acctdemo image and port 9040. For this walk though it would be 172.19.202.52:9040. Yours will be similar. You should be presented by a CICS logon screen like the one below.

RunningMicroFocusEnterpriseServer_7.jpg

  • Now you need to logon to the CICS Region. You can do this by entering SYSAD for the USERID and SYSAD for the Password.
  • Next you need to clear the screen. You can find this on the keymap of the emulator you are using. For x3270 select the Keymap menu option.
  • To launch the acctdemo application type ACCT. You should see the initial screen for the application.

RunningMicroFocusEnterpriseServer_8.jpg

 

  • If you type D for the Request and 11111 for the ACCOUNT, you be taken to some fictional account information. Other account numbers to try are 22222, 33333....

RunningMicroFocusEnterpriseServer_9.jpg

 

  • Finally, to administer the Enterprise Server, type start http:172.19.202.52:86 from a command prompt. This will bring up the Enterprise Server Administration console.

RunningMicroFocusEnterpriseServer_10.jpg

 

Summary

Now you are running and managing a CICS application in a Docker Container. Hopefully this was interesting. In the future we will explore leveraging Kubernetes in Azure (AKS) for orchestrating and managing the containers.