Upgrade Network Installation on IIS to v0.1.2-243

 


Upgrading Multi-user Corporate Network / Team installation of OpenRose - Requirements Management - An Open Source and FREE Requirements Management Application / Tool.

This guide helps users to Upgrade all required software and components to run OpenRose on a network computer(s). It guides users to upgrade 

  • OpenRose WebUI front-end 
  • OpenRose API back-end 

on single / multiple network connected computer(s) and configure it. 

Direct Link to YouTube Video : 

https://www.youtube.com/watch?v=grplzAth_JI

Video Transcript :

Hello once again, and welcome to OpenRose—a FREE and Open Source Requirements Management Application / Tool. You can find more information about OpenRose at 

https://github.com/openrose

In this video, we’re going to talk about how to upgrade your installation of version 0.1.00, which may be installed in a network location using Internet Information Services (IIS).

Let's consider that in my environment, I have the first 0.1 version of OpenRose installed in IIS. I'll start by navigating to my Internet Information Services setup, where I can see OpenRoseAPI and OpenRoseWebUI—two separate applications. They are both listening on different ports in my IIS configuration.

As we know, the OpenRose API communicates with the SQL Server database. In this instance, all these applications are installed on the same computer, Bageera. However, you can install them on separate computers or deploy OpenRose across three different servers if needed.  

For example:

  • Web UI can be hosted on one server.
  • API can be hosted on another.
  • SQL Server can be hosted separately on a third server.

Finding Your Application Files

The first step is to locate where these applications or websites are pointing within my file system. To do this, I simply open File Explorer and navigate to the correct folders.  

I can see that everything is deployed in:  

"C:\inetpub\wwwroot\OpenRoseAPI"

Similarly, the OpenRose Web UI is also available in the same location.

The Web UI points to the API, and the API connects to the database. So, the first thing we need to do is upgrade both the Web UI and the API.

Backing Up Configuration Files  

The Web UI contains an "appsettings.json" file, which defines where the API is located. If I open this file, I can see that it points to the API using the base URL—  

"http://localhost:7673"

Since this is where the API application is running, I need to ensure that my settings remain intact during the upgrade.

To do this:

  • I copy the "appsettings.json" file from my current installed version.
  • I move it into my downloaded files as a backup.

Downloading the Latest Version  

I’ve already downloaded the latest version: "0.1.2-245". This is an internal update that includes a small script change. However, you could also download "version 0.1.2-243", which is publicly available.  

To download, visit:  

https://github.com/openrose/releases

In my case, I’m using the latest Windows operating system, so I’ll use the x64 version. While it's possible to deploy on x86, most users will opt for x64.

After downloading the zip files:

  1. I extract the contents.
  2. I navigate to the API folder and locate its "appsettings.json" file.
  3. I copy this file into my downloaded backup folder to preserve settings.

Similarly, for SQL Server:

  • In my environment, SQL Server is installed on Bageera
  • My connection string points to: "Bageera\SQLExpress"  
  • Since I’m using an environment variable to override the database connection, I don’t need to modify my `appsettings.json` file manually.

Performing the Upgrade  

Now that everything is backed up, I proceed with upgrading:

1. Stop both applications in IIS:

  • OpenRose API  
  • OpenRose Web UI

 2. Delete the existing application files:

  • Navigate to "C:\inetpub\wwwroot\OpenRoseAPI"
  • Delete all files in this folder.  

3. Copy the new files:

  • Move the new API files into "C:\inetpub\wwwroot\OpenRoseAPI"  
  • Restore the original "appsettings.json" file.  

4. Repeat for the Web UI:

  • Delete old files.  
  • Copy new files from the downloaded location.  
  • Restore "appsettings.json" to preserve settings.  

Restarting and Testing  

With everything updated:

  • I restart the IIS applications.  
  • OpenRose API connects to the database and updates the schema automatically if necessary.  
  • I navigate to my local application using:  
            "http://localhost:7673"  

  • OpenRose loads successfully, and I verify the new features in the upgraded version.

The latest release includes enhancements such as Copy Project Item, which improves workflow efficiency.

Conclusion  

That’s how you upgrade OpenRose in a network installation using IIS. You can follow a similar process for standalone installations—just ensure that your configuration files (`appsettings.json`) are correctly preserved during the update.

Thank you for watching! If you found this useful, please share this video with others who may benefit from OpenRose—whether using it for individual, network, or cloud installations.

Thanks, and bye!



Comments

Post a Comment

Popular posts from this blog

Introduction to OpenRose - Requirements Management

Image
Watch it on YouTube at : https://www.youtube.com/watch?v=P0x3ZaHg8sA OpenRose - Requirements Management Application VIDEO TRANSCRIPT Hello, and thanks for joining in for the launch of OpenRose, an open-source requirements management application. The main purpose is to help users and teams "do it right" and ultimately reduce waste. OpenRose is released on GitHub at [github.com/OpenRose](https://github.com/OpenRose). Users can look at the source code and documentation at the same location. Let me do a quick demo of the application. In this environment, I'm using Windows 11 on a desktop computer, not a server. I have installed IIS and deployed a web deployment package over IIS. When you connect to OpenRose, on the homepage, you will see a welcome message like this: "Welcome to OpenRose." One would start by creating a new project. For this demo, I've created two separate projects. The first project is a small example of how I converted a document published b...
Read more

What is Requirement?

Image
What is Requirement? OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=3qQzKbfvRPA Video Transcript :   Hi, welcome to OpenRose, an open-source and free requirements management application. Please visit https://github.com/openrose for more information. Let's go to the project dashboard, and this time, let's open a deep hierarchical level project. This is just a demo project, so when I open that project in the TreeView and start expanding the project, I can see some sample item types along with a Parking Lot, which is the system item type. Inside item type one, I have a top-level item, then item one and item two, which are broken down into further items. You can see I've given the names which indicate a kind of logical hierarchical structure in the name. Here, you can see L1, L2, L3, L4—that's the level. The project is considered as level one, and item ...
Read more

Details View - OpenRose - Requirements Management

Image
    Details View OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=FC67o7lUy3I Video Transcript : Hello. OpenRose is a requirements management application, which is freely available and published on GitHub. Simply go to github.com/openrose to find more. Today, we will discuss the Details View. When you go into the Projects section where you can see your list of projects, there are two main views: the Tree View and the Details View. When I click on Details View, I enter the project one level at a time, or I exit the project one level at a time. Inside the project, we know that there are item types. In this particular view, we can see that I have a parking lot, which is a system item type, and four other item types that I have created. This is a public document published by Barkley's Bank, which I have tried converting into some sort of specification or requirem...
Read more