1. Home
  2. ERP
  3. ADE
  4. Integrate ADE with StarShip

Integrate ADE with StarShip

To set up companies, you will need to point StarShip to the company configuration file in the StarShip Connector. The configuration file is provided by the developer of the interface and must be in place setting up your company in StarShip. It is recommended that you store the file on a network in order to keep it centralized, accessible to all StarShip machines, and to remove any risk of the file being overwritten.

You can also configure additional ADE settings, if necessary.

Configuration File

The company configuration file is defined in the StarShip Connector as follows.

  1. Double-click the shortcut icon on your desktop to open the Connector or launch it from the Windows menu. If the Connector is already running you can launch it from the Windows system tray.
  2. Select the ADE/Developer Interfaces Setup tab.
  3. Click the Add button, then navigate to and select the company configuration file. Click Open.

ADE Settings

Some developers coding against the ADE specification in StarShip v9 made internal references to the station number or path in the StarShip.ini file or registry settings. Although these are no longer used in the current version of StarShip, they will be created to maintain backwards compatibility. If you are installing the StarShip Connector on a new workstation, you may need to modify the values based on the requirements of the integrated application. Consult your interface developer if you require additional detail.

Station Number

The data files exchanged between StarShip and the ADE interface system use the StarShip station number as the input/output file extension. For a single-user version of StarShip, the station number will always be ‘0’. For multiple users where the input path is shared, the station number can be ‘0’ to ‘99’. The ADE interface needs to determine the station number to communicate with StarShip. The station number is maintained in the Connector.

There are two strategies for backwards compatibility when using Station Number as input/output file extension. The option to use depends on whether your setup will allow for using multiple connectors. You may need to consult the developer of your integrated application for the option to use.

  1. Have as many connectors installed as stations, where each connector takes a different station number. In this case, the configuration file can’t be shared. Each Connector will need to have its own configuration file because the Company Name in each configuration needs to be distinct.
  2. Have one connector installed, with multiple configuration files added to that connector. Each configuration file has to have a distinct company name and would have the Station Number hard coded rather than using the dynamic %StarShip9Station% variable.

The company that you select to ship against in StarShip will determine the Station Number that is used and is remembered per user.

Windows Messaging

When StarShip or the ADE interface is waiting for data, they will wait for a windows message indicating that the file is available. Whenever they write a file, they broadcast the registered message. Whenever they are expecting an input file, they wait for the message. The message sent does not contain any information, but simply indicates that the input file is available.

If you would like to use this trigger type, check the Windows Messaging check box.

When not checked, StarShip and the integrated ADE application will poll the hard drive for the input file.

Communications Path

If not already configured, in the Communication Path field, type in or use the Browse button to select a common directory that StarShip and the ADE application can access. Changing the Communications Path will update the configuration file.

ADE Configuration

Save and Restart

After configuring ADE, click the Save & Restart button. The Connector will save your settings and relaunch. Once this is done, you can log into StarShip to add your company.