Configuration

Accessing the Wasp Configuration Tool

Follow the steps below to access the Wasp Configuration Tool:

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

Click on the Wasp.Installer.Configure. Note: Always right-click and Run this as Admin. 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.

Validate the WaspConfig and WaspAuth databases
In “WaspTrack Database Connection”, copy/paste the Writer and Reader passwords from below into the appropriate box, then click each Update button.

Username: dbo_Writer, Password: db0-Wr1ter_P455w0rd

Username: dbo_Reader, Password: db0_Re4der-P455w0rd

Note: If you would like to set your own writer and reader user credentials, this is where you would do so.

Continue to validate each of the tabs. Some tabs will not have a validate button; those can be skipped. For most users, one tab will be blank, depending on which product is installed. This is expected. For instance, if you have AssetCloud On-Premise (only), the InventoryCloud MVC tab will be blank. If you have InventoryCloud On-Premise (only), the AssetCloud MVC tab will be blank.
If there are any errors such as “A task was canceled”, wait for 30 seconds and attempt to validate again (this may need to be done several times). Once all tabs are validated, save and exit the Wasp Config Tool.

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 the firewall.

Note: These bindings and the firewall routing should only allow access to the Wasp_AC or Wasp_IC site. Wasp API and WaspSTS sites need not be exposed to the public.

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.
To view the license information, click on the License tab.

Note: The License tab within the configuration tool permits license entry solely from the machine where the API is installed physically.

List Of Components

Microsoft C/C++ Runtime - The Microsoft Runtime is a prerequisite for most Wasp product components.
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.8 is a prerequisite for most Wasp product components.
Microsoft SQL Server - The Microsoft SQL Server contains all your data.
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.

Note on how the setup updates components that were moved after installation

The On Premise setup can detect if the following components have been moved and will update them in their new location:

STS Authentication Web Service (IIS)
API Business Logic Service (IIS)
AC Web Rendering Service (IIS)
IC Web Rendering Service (IIS)
Now Service (Report rendering and mailing Windows Service)
Later Service (Scheduling Windows Service)

The Database and Redis are not updated by the OnPrem updater. Use the original OEM setups to update these software components.

During Updates, other components, scripts, and tools will be installed according to Microsoft guidelines in the directories specified by the environment variables %ProgramData%, %ProgramFiles%, and ProgramFiles(x86) as appropriate.

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.

WaspConfig Database Connection - Enter the new sa password and click on the “Validate Config DB“ button. Similarly, In the WaspAuth Database (STS) DB Connection, enter the new sa password for the “Business Logic API Password“ and click on the “Validate Auth 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 password:

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

WaspAuth Database (STS) DB Connection

Change the password.
Click on the Validate Auth DB.

Note:

If the SQL Server has the same password for the sa account, both Auth and Config sections MUST MATCH.
Make sure to remember/note the new password. After making the above changes, the user must 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).

Reset User Password

Select the Username from the dropdown list. User Email will get updated based on the username selected from the dropdown list.

Enter the New Password.
Click on the Reset Password button. Note: Make sure to remember/note the new password. After making the above changes, the user must restart the World Wide Web service.

Steps to Change the Application Port Details

The default port for AssetCloud is 8702 and the other ports are 8700 and 8701.

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 and select WASP_AC.
Click on Edit Site > Bindings.

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

To change the port in which the web server 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 Asset Cloud Service.

Update the details.
Click on the Validate MVC.

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

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

Firewall

Use the configure tool to change the MVC URL for the product you installed. Refer steps to configure the 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 HTTP connection using the browser, preferably on the server itself rather than from external clients. After the browser successfully renders the login page via https, then use the wasp configuration tool to verify that the software can access it and to reconfigure the system to use that address in emails, etc.

Following are the steps to configure the firewall:

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

A 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 it matches the details in the Wasp Configuration Tool.

In the Wasp Configuration Tool, click on the Asset 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 part of the Firewall routing and the URL of the firewall is entered where the Port number was.
Click on the Validate MVC. Note: After making the above changes, the user must 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 log in to the AssetCloud OP application.

Note: SMTP server settings must be entered to enable email features such as sending reports, notifications, etc. Refer to Configuring SMTP topic. You can add and invite users without SMTP. Refer to Register Users without SMTP topic.

Register Users without SMTP

Click on Settings > Settings > Email > User Registration Without SMTP.
Click on the "Register users without SMTP" checkbox.

Click on the Save button.
To add users, click on the Users > User > New button. Enter the first name, last name, email address, and role. Click on the "Add & Invite" button.

Configuring SMTP

Click on the Yes button on the pop-up message or Click on Settings > Settings.

Click on 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.)

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

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

In the General section, change Start Mode from OnDemand to Always Running.
In the Process Model section, change Idle Time-out (minutes) from 20 to 0.
In the Recycling section, change the 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.

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

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

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

SQL Server Configuration Manager

The DBs and SQL are only installed using the installer. The following configuration needs to be done manually if the “Connection Failed” error message appears.

Expand SQL Server Network Configuration and select Protocols for WASPDATA. Enable TCP/IP. It will be disabled as shown in the image below.

Right-click on TCP/IP and select Properties. Select the IP Addresses tab and find your IP address of your computer. Remove the value 0 in the TCP Dynamic Ports. Add the value “1433” in the TCP Port. Click Apply & OK.

Select SQL Server Services > SQL Server Browser > Properties. Select Start Mode as “Automatic”. Click Apply and OK.

Right-click SQL Server WASPDATA and select Restart.

Stop and Restart All Services (Bounce)

Procedure to stop and restart ("bounce") all of the services for Cloud On-Premise, then recycle the IIS app pools:

Stop services in this order

Redis
SQL Server (WASPDATA)
WASP Later Service
World Wide Web Publishing Service

Start services in this order

SQL Server (WASPDATA)
World Wide Web Publishing Service
Redis
WASP Later Service
Wasp Now Service

Recycle Cloud OP (On-Premise) application pools in Internet Information Services (IIS) Manager

At the upper left, click Application Pools.
In the right pane in the Name column, right-click each of the three following names, then click Recycle. Notes: Do not click the similarly-named "Recycling". You will not see any feedback. There may be a slight pause before the system becomes responsive for the next task. The order does not matter. Names:

WaspPAPI
WaspPMVC (for earlier versions)
WaspPAC (For newer AssetCloud installs)
WaspPIC (For newer InventoryCloud installs)
WaspPSTS

==============================================================================

If you want to make a batch file that will do this, include the lines below in a file called "Bounce OP Services (Admin).bat". When you need to run the file, right-click on it and Run As Administrator. The pause command at the end allows you to review the results before closing the command prompt.

Note: Because different versions have differently named Sites and Application Pools, there are 3 different potential batch files to accomplish the above.

============================================================================

RabbitMQ and Erlang are no longer required for AssetCloud v02.01.05 or Newer.

============================================================================

AssetCloud v1.04.05 or earlier

net stop RabbitMQ

REM - stopping Rabbit also stops WaspNowService

net stop Redis

net stop MSSQL$WASPDATA

net stop WASPLaterService

net stop W3SVC

net start MSSQL$WASPDATA

net start W3SVC

net start RabbitMQ

net start Redis

net start WASPLaterService

net start WaspNowService

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspSTS"

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspAPI"

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspMVC"

::Flush Redis

cd C:\Program Files\Redis-3.0.504-64bit

redis-cli -h 127.0.0.1 -p 6379 -a r3dIkul00zSVmVs flushdb

redis-cli -h 127.0.0.1 -p 6379 -a r3dIkul00zSVmVs flushall

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspSTS"

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspAPI"

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspMVC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPAPI"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPMVC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPSTS"

pause

::end code::

============================================================================

AssetCloud v2 or Newer::

net stop RabbitMQ

REM - stopping Rabbit also stops WaspNowService

net stop Redis

net stop MSSQL$WASPDATA

net stop WASPLaterService

net stop W3SVC

net start MSSQL$WASPDATA

net start W3SVC

net start RabbitMQ

net start Redis

net start WASPLaterService

net start WaspNowService

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspSTS"

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspAPI"

%windir%\system32\inetsrv\appcmd stop site /site.name:"Wasp_AC"

::Flush Redis

cd C:\Program Files\Redis-3.0.504-64bit

redis-cli -h 127.0.0.1 -p 6379 -a r3dIkul00zSVmVs flushdb

redis-cli -h 127.0.0.1 -p 6379 -a r3dIkul00zSVmVs flushall

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspSTS"

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspAPI"

%windir%\system32\inetsrv\appcmd start site /site.name:"Wasp_AC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPAPI"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPAC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPSTS"

pause

::end code::

============================================================================

Asset & InventoryCloud v2 Installed on the Same Machine

net stop RabbitMQ

REM - stopping Rabbit also stops WaspNowService

net stop Redis

net stop MSSQL$WASPDATA

net stop WASPLaterService

net stop W3SVC

net start MSSQL$WASPDATA

net start W3SVC

net start RabbitMQ

net start Redis

net start WASPLaterService

net start WaspNowService

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspSTS"

%windir%\system32\inetsrv\appcmd stop site /site.name:"WaspAPI"

%windir%\system32\inetsrv\appcmd stop site /site.name:"Wasp_AC"

%windir%\system32\inetsrv\appcmd stop site /site.name:"Wasp_IC"

::Flush Redis

cd C:\Program Files\Redis-3.0.504-64bit

redis-cli -h 127.0.0.1 -p 6379 -a r3dIkul00zSVmVs flushdb

redis-cli -h 127.0.0.1 -p 6379 -a r3dIkul00zSVmVs flushall

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspSTS"

%windir%\system32\inetsrv\appcmd start site /site.name:"WaspAPI"

%windir%\system32\inetsrv\appcmd start site /site.name:"Wasp_AC"

%windir%\system32\inetsrv\appcmd start site /site.name:"Wasp_IC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPAPI"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPAC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPIC"

%windir%\system32\inetsrv\appcmd recycle apppool /apppool.name:"WaspPSTS"

pause

::end code::

============================================================================

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

US Toll Free

Tech Support Numbers: 866-547-9277 option 3 and 214-547-4100 option 3.

Web/Cloud License expiration numbers: 866-547-9277 option 2 and 214-547-4100 option 2.

On-Premise License Activation (Sales) numbers: 888-536-7067 and 214-547-4100 option 2.

0845 430 1971

Website

http://support.waspbarcode.com/