thingworx foundation server #6

Description

Install Thingworx Foundation Server on Ubuntu


Overview

This charm provides Thingworx Foundation Server. The scope of this product is beyond what can be reasonably described here. To learn about Thingworx by PTC you should see their Developer Portal. If you are already familiar and just want to try the Foundation Server you will need to get a copy of the trial edition. If you haven't alrady register for a developer account. After registring download the Trial Edition and you're ready to go.

Deploy

To deploy:

juju deploy cs:~chris.sanders/thingworx-foundation-server --resource foundation-server=./path/to/Thingworx.zip

Check the status of the deploy with:

juju status

Note the IP Address for the machine in use. By default this will get you up and running with HTTPS access on port 443 available to access the tomcat instance. For easier access you can enable HTTP access on port 80 with a configuration option, see all of the configuration options at the bottom of this page.

After deployment completes, the tomcat server will load the Thingworx application which can take a minute on the first boot. Once it is ready you can access it at http://ip-address/Thingwox using the Username and Password. The admin username and password are provided in the Thingworx [Installation guide][install-guide] and at the time of this writting are

Username: Administrator

Password: admin

If you can not access the Foundation server you can check the status to see if it is running by accessing http://ip-address/manager/html, the default password for tomcat is "tomcat8" for both the user and password.

Scale out Usage

This charm does not adderss multi-server configurations at this time. However, you can add units to stand up multiple servers if you would like to test migrations or simply want multiple indipendent test servers.

Known Limitations and Issues

This is a first pass at this charm, there are improvements that I would like to make but it is valuable already. Configuration parameters do not alter an already installed server. For example, chaning the HTTP port or setting the charm to HTTPS only will not have any affect on an already deployed server. This is easily addressed, and it's on my to-do list when I have time.

Note this charm is not installing ntp as recommended. When running on a local LXD this is not necessary and ntp can be easily added if your install in an environment that needs ntp. If you want to add ntp in your bundle on even after deploy you can run:

juju deploy ntp
juju add-relation thingworx-foundation-server ntp

Configuration

Configuration options are fairly self explanatory at this time. If you are installing in an insecure environment you should consider setting the follwoing.

  • install-admin=False
  • https-only=True

This will not install the tomcat admin package and not configure tomcat to use port 80 so all traffic is HTTPS.

Contact Information

Upstream Project Name

Configuration

tomcat-user
(string) The user added to tomcat
tomcat8
https-only
(boolean) Only allow https access
True
https-port
(int) Port for https access
443
install-admin
(boolean) Include the tomcat8-admin package for /manager access
True
http-port
(int) Port for http access
80
tomcat-passwd
(string) The tomcat user password
tomcat8