Sign in

Introducing

Ideagen Community

Introducing

Ideagen Community

Articles in this section

See more
  1. Q-Pulse
  2. Q-Pulse Windows
  3. IT Guide
  4. Upgrading

Technical Considerations for Upgrading to Q-Pulse 7 Web

Alan Blair
  • Updated
Follow
Who is this article for?

 IT Personnel planning an upgrade to Q-Pulse 7 web.

 IT knowledge access required.

Q-Pulse is a Windows-based N-tier application that has been built on the Microsoft .NET Framework. The system runs using windows services on an application server along with IIS website to provide access via a data portal. All data is stored within the SQL Server.

While performing an upgrade it is recommended to review the minimum requirements and confirm that the new version your are upgrading to will not only run but perform well on your existing infrastructure.

This article explains the technical footprint of Q-Pulse and provides some considerations when planning an upgrade. This has been split into 4 sections:

  1. The Q-Pulse Footprint
  2. Specific Changes
  3. Pre-Upgrade Checks
  4. Further Reading

1. The Q-Pulse Footprint

When using the Q-Pulse Windows client, resources such as RAM and CPU are usually split between the application server and the client PC. Some tasks and actions are processed by the client whilst others are processed on the application server.

However, when using the Q-Pulse 7 Web interface all of this processing needs to be done on the server (as there is no client in use and you are interacting with a website hosted on the application server). This means the server resources required to operate the web interface are significantly higher than if you were using the Q-Pulse Windows client alone.

Essentially, the technical footprint of the application has increased.

For this reason, if you intend to use the Q-Pulse 7 web interface after your upgrade then you must review the server specifications and plan the necessary upgrades/migrations of your Q-Pulse application server.

In some instances you will be able to upgrade your server to meet the requirements but in others you may need to consider moving Q-Pulse to a totally separate server or environment.

Need to review the minimum requirements? Visit our guide Q-Pulse 7 Hardware & Software Requirements.

2. Specific Changes

The below changes should be considered:

 

Footprint.png

3. Pre-Upgrade Checks

Before performing an upgrade it is important to perform the below checks:

  1. Confirm that your server and end user hardware still meet the minimum requirements. These requirements are available on the Q-Pulse 7 Hardware & Software Requirements article.
  2. Review your usage of the system and planned usage of any new features being introduced.
      • If possible, these new features should be tested on a separate testing environment prior to going live.
      • Consultancy, configuration and training services are available from the Ideagen professional services team. Please visit our contact page to request details on these services.
  1. Review your diskspace on the SQL server and confirm you have enough space to continue your planned growth.

What Next?

With the application server successfully upgraded you are ready to upgrade a client and test the system is functioning. Please see How to Prepare for a Q-Pulse Upgrade for the next steps or How to Perform a Q-Pulse 7 Upgrade to review the whole process.

4. Further Reading

Article Comments

0 comments