{"id":10877,"date":"2020-06-14T14:42:10","date_gmt":"2020-06-14T18:42:10","guid":{"rendered":"https:\/\/www.carnaghan.com\/?p=10877"},"modified":"2020-10-19T13:16:22","modified_gmt":"2020-10-19T17:16:22","slug":"standing-up-opentext-appworks-20-2-docker-containers-in-10-minutes","status":"publish","type":"post","link":"https:\/\/www.carnaghan.com\/standing-up-opentext-appworks-20-2-docker-containers-in-10-minutes\/","title":{"rendered":"Standing up OpenText AppWorks 20.2 Docker Containers in 10 Minutes"},"content":{"rendered":"\n

The latest version<\/span> of OpenText AppWorks Cloud Edition (CE) 20.2<\/a> was recently released and promises to improve “developer<\/span> agility through simplification and improved visibility with a new List Designer, new Action Bar Designer and added support for full translation of layouts.” In addition this release comes available packaged in a Docker container, which makes it much easier to setup locally as a development environment or to simply try out the new features of this release.<\/p>\n\n\n\n

Grabbing the Download<\/h2>\n\n\n\n

If you are a licensed customer<\/span>, you can grab a copy of the containerized<\/span> version<\/span> of AppWorks directly via your OpenText MySupport<\/a> portal by navigating to Resources -> Downloads -> AppWorks Platform. The 20.2 release provides complete documentation as well as a Linux, Windows and Container download. In addition to this you’ll need to have your license information handy including your registered customer name, site name, and license key. The documentation OpenText provides is more than enough to get you up and running quickly and also provides in-depth information should you need to customize your setup. <\/p>\n\n\n\n

Configuring Docker<\/h2>\n\n\n\n

My experience<\/span> was generally straight forward on my local computer (which happens to be a MacBook Pro). You will need to install Docker<\/a> and I highly encourage you to review the quick start guide<\/a> if you are unfamiliar working with containers. One snag I hit early on was with my Docker version<\/span>. I was running edge, which is the latest and greatest, but also prone to bugs or other issues. After I installed<\/span> the stable release I was able to successfully follow the instructions and get AppWorks up and running correctly. In order to successfully run AppWorks, you will need. a minimum of 4096Gb assigned to your containers. To ensure you have enough memory, I highly recommend reserving at least 6Gb to ensure you have enough to run all of the associated containers.<\/p>\n\n\n\n

\"\"
Docker Resource Settings<\/figcaption><\/figure>\n\n\n\n

Setting Environmental Variables<\/h2>\n\n\n\n

After you have downloaded the container archive from OpenText MySupport (see above), you will need to untar it by issuing the command below. Make sure you have placed the tar<\/span> file inside the directory you will to unarchive its contents (for example I created ~\/code\/appworks and ran the command from that location).<\/p>\n\n\n\n

tar zxvf appworks-platform-20.2-containerization.tar<\/code><\/pre>\n\n\n\n
You should end up with the following directory structure:<\/p>\n\n\n\n
\"\"
AppWorks Directory Structure<\/figcaption><\/figure>\n\n\n\n
Next you will need to add your registered customer<\/span> name, site name, and license key as environmental variables in your local version<\/span> of AppWorks. First of all open the .env file to modify the customer<\/span> name and site name variables. You should be able to edit this using your favorite text editor.<\/p>\n\n\n\n
\"\"
AppWorks License Information<\/figcaption><\/figure>\n\n\n\n
Note: you do not need to wrap either of these in quotes. Once you have saved your .env file, navigate over to env\/secrets. In here you should see the following files:<\/p>\n\n\n\n