Download and Install Transtream
Once your environment is prepared and meets the requirements, download the Transtream setup and install it on a server.
Get Transtream Setup
- Download and install Transtream Setup. This is available from the Downloads page.
- Start Transtream Setup. You are prompted for confirmation. Click OK to proceed.
- In the Settings dialog, provide your Cloud credentials and, if required, Proxy details, and click Save.
Staging
Typically, you will not use the staging settings. See Staging for details on access to pre-production software.
Once saved, Transtream Setup itself is available for use. On initial installs, it will have no detail other than the Server entry with the default installation folders for Transtream and HubCapp.
Install Key Points
- The latest version of Transtream Setup released with version 8.45.0 will only allow HTTPS installs.
- Current on-premise instances can be updated to HTTPS binding using the latest version of Transtream Setup.
Configure the server
- In the tree, right-click Servers, and select Add Server. A server entry with the same name as the machine being used is created.
- Click Apply to confirm the name of the server (you can change it if required). In the tree, the server will now include four setting groups: Application Pools, IdP Instances, Transtream Instances, and HubCapp Instances.
Add an Application Pool
- Right-click Application Pools, and select Add Application Pool.
- Give the Application Pool a unique Name, and click Apply.
Once you have an Application Pool, you can add as many instances as required.
Add a Transtream instance
- In the tree, right-click Transtream Instances, and select Add Transtream Instance.
- Complete the configuration.
Key settings include:
- Host Name in the Binding Settings group. This is the URL that will be used to access the instance. It must be unique. When you run the install, Transtream Setup will create this site in IIS.
- The Compliance Engine group. By default, a new Logistics Server is created. However, you can point the Transtream instance to an existing Logistics Server endpoint.
- The Storage group. Here you provide details of the SQL Server instance that will be used.
- The Identity Provider group. Here you must provide a valid Pierbridge IdP Url.
For full details on all settings, see Transtream Setup reference.
- Click Apply to validate the configuration, and then add your license token and click OK to submit your license request.
- In the Contact Confirmation dialog, select the contact and click OK. This populates the License Key field.
Add a HubCapp server instance
HubCapp lets users use their own devices and data sources. Through locally installed agents, they can connect to a HubCapp server and use their own printer, scale (Peripheral Agent), or data sources (Data Agent). If you require this capability, add a HubCapp server instance (it can be added later if required).
- In the tree, right-click HubCapp Instances, and select Add HubCapp Instance.
- Complete the configuration, and click Apply. Like the Transtream instance before, at this point you will be prompted for your license token. On success, the License Key field will be populated with the license that you need to supply to your users in order for them to successfully connect.
Host Name is the key setting. This is the URL that will be used to access the HubCapp server. It is used by IIS; and must be unique. For full details on all settings, see Transtream Setup reference.
Run the install
Once you have the Transtream instance configured and applied (saved), you can run the install to create the actual instance on the server.
On the Install menu, click Run Now (or press Ctrl R). You are prompted for confirmation. Click Yes to proceed. Transtream Setup executes a PowerShell with your configuration. You can see the progress.
Test\complete the installation
To test Transtream instances, in the tree, right-click an instance and select Browse. This opens Product Admin from where you can open the Administration App and add users and locations, and onboard carriers. Specifically, when configuring a new instance, to attain the capability to ship, you should proceed in this order:
- Add a location.
- Add a user.
Users and emails
If you want Transtream to send emails to your users supplying them with their login details and link, in the Administration App's Data page, on the Mail Settings tab, you can provide details of the SMTP service you are using to send emails. See Set up Email.
You may not want to add all your users until you have onboarded carriers and tested the installation. Users can also be imported. See Users and Import Users for more details.
- Onboard a carrier.
- Add a default label. Even if Setup My System is showing this as done, we recommend adding a default label that can be used by all carriers. If onboarding a carrier has created labels for that carrier, Setup My System will show this step as done, regardless of whether the label is generally usable.
The Administration App includes a Setup My System feature that guides you through this. If your carrier is not listed under Setup My System, you will need to onboard it manually. Each carrier's topic in this site includes manual setup guidance.
The Administration App is downloaded as part of the installation, and you can manually download other Apps, such as Warehouse and View. See Use Product Admin for details.
- The login credentials for a new Transtream instance are set in the instance configuration (the User Credentials settings).
- When you start Transtream instances for the first time, it can take a few moments as the database is created. Subsequent starts take less time. However, if nothing loads, check that IIS has started the site.
- If, for testing, you have installed locally, see the Host Name entry (Binding Settings group) in Transtream Setup reference for information on modifying your hosts file to resolve to your local machine.
If you are using HubCapp to access local scales, printers or data sources, download Peripheral Agent or Data Agent and connect to your HubCapp server. Any of your users who want to use local devices or data sources will also need to install the agents on their machines. See Install Peripheral Agent and Install Data Agent.
