Configuration

Configuration

• Accessing the Wasp Configuration Tool
• List of Components
• How to assign a password to the Database sa account
• Steps to Update the Database Password
• Steps to Update the Admin User Password
• Steps to Update the Application Port Details
• Firewall
• SMTP Settings
• IIS Application Pool Settings

Maintenance

Troubleshooting

Configuration

Accessing the Wasp Configuration Tool

Follow the steps below to access the Wasp Configuration Tool:

• Path - C:\Program Files\Wasp Barcode Technologies\Wasp On-Premises Software\License\configure
• Search for Wasp.Installer.Configure.

• Click on the Wasp.Installer.Configure. Enter the password and click on the Ok button.

Note: The password will be shared by the Wasp team along with the package

• The Wasp Configuration Tool will appear.

Note: We recommend deploying Wasp Cloud products behind a firewall and routing filtered traffic through to the IIS server with the Wasp Cloud MVC site. This practice usually changes the entry point URL of the application. In cases like this or any other change to the app URL two changes are required:

• Use the configure tool to change the MVC URL for the product you installed. Refer steps to configure firewall.
• To use Mobile devices you will need to manually update a file. The file C:\inetpub\wwwroot\WaspMVC\Mobile\weblink.x can be edited using notepad or any text editor. The url in the <Download> link tag will need to be updated to use the MVC URL as well.

List Of Components

• Microsoft C/C++ Runtime - The Microsoft Runtime is a prerequisite for most Wasp product components.
• Erlang Queue component - The Erlang Queue component is required for scheduled reports and notifications like checkout overdue.
• RabbitMQ Queue component - The RabbitMQ Queue component is required for scheduled reports and notifications like checkout overdue.
• Wasp Queueing Service (Later) - The Wasp Queueing Service (Later) windows service is required for scheduled reports and notifications like checkout overdue.
• Redis Session Cache - Fast Cache for all web servers and other components.
• Microsoft .Net 4.8 - The Microsoft .Net 4.6.2 or higher is a prerequisite for most Wasp product components.
• Microsoft SQL Server - The Microsoft SQL Server contains all your data.
• Microsoft SSMS - The Microsoft SQL Server Management Studio can be used to create regular backups of your data and much more.
• Wasp Rendering Service (Now) - The Wasp Rendering Service (Now) windows service is required to mail scheduled reports and notifications like checkout overdue.
• Wasp Secure Token Service (STS) - The Wasp Secure Token Service (STS) Web Service manages Authentication for all other Wasp components.
• Wasp Business Logic Service (API) - The Wasp Business Logic Service (API) Web Service provides business logic services for other Wasp components.
• Wasp Asset Cloud Service (MVC) - The Wasp Asset Cloud Service (MVC) Web Service manages the web interface for Asset Cloud.
• Wasp Inventory Cloud Service (ICMVC) - The Wasp Inventory Cloud Service (ICMVC) Web Service manages the web interface for Inventory Cloud.

How to assign a password to the Database sa account

Changing your database password is an important step in securing your system.

Warning: Changing the Database password, or any other configuration parameter may cause disruptions to any currently running OP instance. Please plan ahead for downtime because any changes done using the configuration tool generally require you to reboot the system. Plan ahead.

We provide a configuration tool to help you configure Wasp On-Premise software with the new sa password and much more.

To change the sa password for the database:

• Connect to the Database using Windows Authentication.

• Edit the properties of the sa user.

• Change the password.

• Start Wasp.Installer.Configure.exe and select “Windows Authentication” and log in

• Enter the new sa password for the “Secure Token STS Password” and click on the “Validate Auth DB” button. Similarly, enter the new sa password for the “Business Logic API Password“ and click on the “Validate Config DB“ button.

• Click on the Save button.
• Reboot the system.
• After rebooting the software will boot using the new password.

Note: Now that you’ve set the sa password, you can retrieve it any time by running the configuration tool on the database, logging in using “Windows Authentication” and clicking on the “Show Passwords” checkbox. The “Show Password” option will NOT be available until you assign your own sa password.

Steps to Update the Database Password

To change the SQL Server account password:

• In the Wasp Configuration Tool, click on the SQL Server.

• Change the password in the Secure Token STS Password. Note: Click on the Show Password checkbox to view the password.
• Click on the Validate Auth DB.

Note:  If the database has the same password for the sa account, both Auth and Config sections MUST MATCH.

Note: Make sure to remember/note the new password. After making the above changes its important for the user to restart the World Wide Web service.

Steps to Update the Admin User Password

To change the admin user password:

• In the Wasp Configuration Tool, click on the Secure Token Service (STS).

• Change the password. Note: Click on the Show Password checkbox to view the password.
• Click on the Validate STS.

Note: Make sure to remember/note the new password. After making the above changes its important for the user to restart the World Wide Web service.

Steps to Change the Application Port Details

The default port for InventoryCloud is 8083.

Warning: If you just installed your On-Premise version and you need to change the port number, do that before you start inviting users.

To find the default port:

• Open Internet Information Service (IIS).
• Click on Sites >MVC.
• Click on Edit Site > Bindings.

• Site Binding screen will appear, and it will display the default port.

• To change the port in which the webserver is exposed, click on the Edit button in the Site Bindings screen. Change the port number and Save it.

Note: We generally do not recommend users change these values without consulting Tech Support. But If you are changing the port number in IIS, make sure that the port number should match with the port number in the Wasp Configuration Tool.

• In the Wasp Configuration Tool, click on the Inventory Cloud Service.

• Update the Port details.
• Click on the Validate ICMVC.

Note: Make sure to remember/note the new Port Number. After making the above changes its important for the user to restart the World Wide Web service.

The user should reboot the machine after making changes in this tool.

Firewall

Note: We recommend deploying Wasp Cloud products behind a firewall and routing filtered traffic through to the IIS server with the Wasp Cloud MVC site. This practice usually changes the entry point URL of the application. In cases like this or any other change to the app URL two changes are required:

• Use the configure tool to change the MVC URL for the product you installed. Refer steps to configure firewall.
• To use Mobile devices you will need to manually update a file. The file C:\inetpub\wwwroot\WaspMVC\Mobile\weblink.x can be edited using notepad or any text editor. The url in the <Download> link tag will need to be updated to use the MVC URL as well.

When setting up https please verify the https connection using the browser, preferably on the server itself than from external clients. After the browser successfully renders the login page via https than use the wasp configuration tool to verify that the software can access it and to reconfigure the system to use that address in mails etc.

Following are the steps to configure Firewall:

• Open Internet Information Service (IIS).
• Click on Sites >MVC > Edit Site > Bindings.
• Site Binding screen will appear, and it will display the Type, Host Name, Port, IP Address and Binding Information, if any.

Note: We generally do not recommend users change these values without consulting Tech Support. But If you are changing any of the details in IIS, make sure that the it matches with the details in the Wasp Configuration Tool.

• In the Wasp Configuration Tool, click on the Inventory Cloud Service.

• Update the MVC Server URL.

Note: The firewall change overwrites changes to the port configuration in the Wasp Configuration Tool because the Port number becomes the part of the Firewall routing and the URL of the firewall is entered where the Port number was.

• Click on the Validate ICMVC.

Note: After making the above changes its important for the user to restart the World Wide Web service.

• The user should reboot the machine after making changes in this tool.

SMTP Settings

SMTP configuration is the first step that you should do once you login to the InventoryCloud OP application. Without this configuration, the user will not be able to send an invitation to users.

Click on the Configure button or Click on the Settings > Settings > Email.

Enter the SMTP details and click on the Validate SMTP button.

Once the SMTP validation is successful, you will be able to send an invitation to other users.

IIS Application Pool Settings

After the Cloud On-Premise software is installed successfully and you have confirmed you can log in successfully, make these changes in IIS Manager to improve performance. (Some settings may already be at the recommended value.)

1. Start Internet Information Services (IIS) Manager (type IIS into the Windows search box to find and launch).
2. On the upper left, expand your computer name, then click on the Application Pools.
3. In the right pane, right-click WaspPAPI, then Advanced Settings.

The Advanced Settings screen will appear. Make the following changes: Configuration

4. Under the General section, change Start Mode from OnDemand to Always Running.
5. Under the Process Model section, change Idle Time-out (minutes) from 20 to 0.
6. Under the Recycling section, change Regular Time Interval (minutes) from 240 to 0. (another suggested value is 1740).The Recycle Time can be set to a specific time you would like IIS to recycle the App pool. Recycling the app pool will cause the very first load to be slower as the Web application loads into memory.

7. Click Ok.
8. Repeat Steps 3 to 7 for the WaspPMVC and WaspPSTS application pools. The settings are same as WaspPAPI.
9. On the upper left, expand Sites.
10. Under Sites, right-click WaspAPI, Manage Website, then Advanced Settings.

11. Under the General section, change Preload Enabled from False to True.

12. Click OK.
13. Repeat Steps 9 -12 for the WaspMVC and WaspSTS sites. The settings are same as WaspAPI.
14. When all 3 application pools and all 3 sites have been updated, IIS Manager can be closed.

Maintenance

If you expose your server to the Internet we recommend regularly monitoring your server for intrusions and other suspicious activity. Wasp Barcode Technologies can not be held responsible if someone breaks into your server nor for any damages incurred.

IIS Logs and other logs can accumulate over time eventually filling your hard drive. You can find a sample - how you can automatically clean up these logs on your installation media under CommonAppData\Wasp Barcode Technologies\MobileAssetWeb\CleanupLogs.

Troubleshooting

Many components of the Installation rely on “.bat” files that can be manipulated if necessary, to run successfully on the target server. If this becomes necessary, we recommend users copy the setup to a Hard drive where the .bat files can be edited so the setup can be retried – but only at the direction of our Tech Support.

The Setup is very good about skipping steps that have already succeeded and resuming/retrying the last step that failed.

The setup also documents the installation process in a series of installation logs. These must be shared with Tech Support if problems arise.

Tech Support Details