# Getting started

## Installation

To install Portal 2, use Novacura Flow Server Manager tool. 

#### Parallel installations

The old Portal and Portal 2 can be installed in parallel and the setup from the old Portal can be migrated to Portal 2 with the export/import functionality. 

Read more under [Migrate existing solution](#migrate-existing-solution).

#### License

Portal 2 will use the same license as the old Portal, if the portal client is available in the license, Portal 2 will be available to use as well. 

### New installation

Portal 2 can be added during the regular new installation procedure of Flow.

To include Portal 2 in the new installation, make sure to tick the box called Novacura Flow Portal 2.

<div align="left"><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-MOHU7-5A-hfCBbDqPS3%2F-MOHZXWU8blv34dwQg4y%2Fimage.png?alt=media&#x26;token=b4d654e8-576a-4a1e-bc1e-26d155465820" alt=""></div>

Follow the instructions in the installation guide.

During installation of Portal 2, base URL is requested. This is the external URL that should be used but only in base form. See below.

{% hint style="info" %}
**Enter the base URL:** \
E.g. [https://myserveraddress](https://address) or [http://myserveraddress:80](http://serveraddress),\
like, <https://novacuraflow.com> or <http://app01:80>.
{% endhint %}

**Flow Auth. URL**

During installation, it is also possible to enter URL for Flow Authentication. This is not a mandatory step but can be used if Novacura Flow Authenticator has also been installed as a component.

More information about [Flow Authenticator](https://help.novacuraflow.com/installation-and-upgrade/windows-authentication).

Read more about Flow installation below:

{% content-ref url="../../installation-and-upgrade/new-installation" %}
[new-installation](https://help.novacuraflow.com/installation-and-upgrade/new-installation)
{% endcontent-ref %}

### Upgrade environment

Portal 2 will be available from version 6.11.10.

To install Portal 2 for an already existing environment, start by upgrading the environment to 6.11.10 or higher. When this is done, go to add component and select Portal 2.&#x20;

Read more about how to add components here:&#x20;

{% content-ref url="../../installation-and-upgrade/add-component" %}
[add-component](https://help.novacuraflow.com/installation-and-upgrade/add-component)
{% endcontent-ref %}

## Managing Portal 2 upgrades and versions

From Flow version 6.13, Portal 2 will have its own versions allowing separate upgrades.

To manage Portal 2 and upgrade to later version, go to "Manage Portal 2" in the menu for the installed environment.

<div align="left"><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-MOHdldXRBPtraFFYYVm%2F-MOHg9Udhv757YDb7qtQ%2Fimage.png?alt=media&#x26;token=e89a7159-9231-4606-a4ab-25b67c87c064" alt=""></div>

If an update for Portal 2 exists, it will be shown in the manager. To upgrade to latest version, click Install. The manager will upgrade Portal 2 to latest version compatible with the Flow Server.

If a specific version is requested or an offline upgrade is needed, it is also possible by downloading the required packages and then selecting them using the Perform offline installation.

<div align="left"><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-MOHhGHs3Hxj0K3o9P8n%2F-MOHhaOBmRV_G5F0jARe%2Fimage.png?alt=media&#x26;token=ddbe6a7c-8c68-4556-b864-490b73c59fd3" alt=""></div>

## Migrate existing solution

Setups from the old Portal can be migrated to Portal 2 by importing pages. During import, a migration will run which will convert the old Portal into Portal 2. Once the migration is complete, the user will receive a downloadable report with a list of found issues and/or required configurations.&#x20;

To run the migration, start by exporting the desired tabs from old Portal.

<div align="left"><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M0wspndbP4nMnHYM7OB%2F-M0wx4fU2us8ohQ5qb7a%2Fimage.png?alt=media&#x26;token=f8253739-dc03-4a08-baa8-2b8fe0caabc2" alt=""></div>

Once the tabs have been exported, go to Portal 2 and select *Import* from the Add section of the admin panel.

<div align="left"><figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FQb0dSNpY9CQ0vdn0sB7Q%2Fimport.png?alt=media&#x26;token=1d01e5b5-c0a2-4272-a245-1d42bcf09587" alt=""><figcaption></figcaption></figure></div>

Select the files containing the tabs to be imported by clicking *Browse* or by dragging and dropping the file in the designated location.

<div align="left"><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M0wspndbP4nMnHYM7OB%2F-M0wxlaPu2sw1iGdRLYg%2Fimage.png?alt=media&#x26;token=f7fdc88b-b9fb-4bf3-9dca-5fd7b3ac649f" alt=""></div>

The import will now try and map the connectors and workflows used. If the names of the connectors and workflows are found, they will automatically be suggested. If the names are not found, the user will need to select the correct names from the drop-down lists.

<div align="left"><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M0wspndbP4nMnHYM7OB%2F-M0wyBOY8mdjJTr0iH7c%2Fimage.png?alt=media&#x26;token=e5785fe6-80fc-443a-94ef-f478197be083" alt=""></div>

Once the connectors and workflows have been selected, click *Import* to start the import and migration. If issues have been detected, a report with issue details will be presented. The report can be viewed on-screen or exported using the *Excel Export* button.

Click *Close* and the migration will be completed. The Portal will now automatically be refreshed to include the new pages.

### Limitations

Some features or configurations may not be available in Portal 2 since they no longer exist, are still under development, or now work differently. These differences will be presented in the migration report, along with a suggested solution or a note to inform the user that that functionality has not yet been implemented.

## System requirements

Portal 2 is supported in any of the following web browsers :

* Microsoft Edge (latest version)
* Google Chrome (latest version)&#x20;

Information about latest release for these web browsers can be found on vendor's website.

{% hint style="info" %}
Mobile devices such as smartphones and tablets are not supported.
{% endhint %}