Note

It is highly recommended to backup your database and the file structure of your Manager instance before processing the upgrade. This
enables you to restore your scenario in any case of errors.
Read chapter Backup and Restore for more information on backup processes in Manager Operations Guide.

Recommendation
Use the Messages functionality to notify your users about the upcoming upgrade and appeal them not to connect within a defined
time range. Although current connections will by closed while upgrade without negative impact you can reduce user-sided confusion
and speed up Tomcat processes due to less active user sessions by doing so.

Additionally consider to specify time range widely enough for running tests on your scenario after upgrade. The upgrade itself will take
approximately 10 - 15 minutes, depending on your network speed and the location you are loading the upgrade installer from.

3.1 Procedure

Proceed as follows to upgrade your Manager instance.

Replace Manager application instance

1. Launch the Tomcat Web Application Manager page by entering the following path in your browser's address
bar, replacing the values in brackets with the according values of your scenario:
http://<your_servername>:<your_port_number>/manager/html
2. Look for the entry of your existing Manager instance within the list of installed applications.

3. Open the folder location your new Manager installation file (*.war) is located at and rename it with the string
displayed in the column Path (without the prepended slash "/").
4. Return to the Tomcat Web Application Manager and select Undeploy in the Commands column of
your Manager instance.
5. Confirm the appearing prompt message and wait until the page has reloaded.

6. Scroll down to the section Deploy and select Browse in subsection WAR file to deploy.

7. Browse to your renamed installation file and select it.

8. Select Open to confirm your selection.

The path to the file is now displayed in the input field.

9. Select Deploy.
The installation file is now uploaded and integrated into the server environment.

Configure new Manager instance

1. Once the page has reloaded select the list entry of your newly deployed Manager instance.

2. Enter the credentials of the initial user (see Prerequisites) into appearing dialog box.

3. Confirm the EULA.

4. On page Step 1 - SQL Server connection enter server address and credentials of the database server as
used in previous installation. Select Next step to proceed.
 5. On page Step 2 - Database creation expand the dropdown select existing database and select the database
your previous Manager instance was connected to. Select Next step to proceed.
6. All fields within the next steps will now display the values as stored in the database. Check the values for
correctness and select Next step to proceed within steps.
7. Having done all steps the upgrade wizard will automatically appear, displaying the page Step 1 - Check
versions.
Since your new Manager version and the version of the database are different it will provide the functionality
to update the database to fit new version requirements. Select Update Database to proceed.
8. Selecting Update Database once again to confirm the database update on page Step 2 - Verify Manager Update.

9. Depending on your database size the update process might take a little while. Wait until the page Step 3 -
Update is loaded, displaying the results of the update process.
10. Select Manager to close the upgrade wizard and load the logon page of your Manager instance.
Do not select the links to import user data. Since not all functions have been updated by now, user import
functionality might result in errors.
11. Restart the Tomcat service to avoid malfunctions invoked by older functions of the previous Manager
instance which are still loaded within the server cache.

Caution
After having updated the database do not connect to the database using an older version of the Manager application. This might
destroy your data stored in the database.
1 Migrating a Workarea

Migrating a workarea allows you to update the workarea resources to a newer SAP Enable Now version. The
migration is necessary, as a newer version of SAP Enable Now includes changes in the resources and the
resource structure. During the migration the resources will be changed to the new requirements. The migration
does not change the content of the workarea.

Resource revisions

Resources will be migrated based on the revision number of each resource. A resource with a changed revision
number will be migrated, for example, revision number is changed from 1 to 2. A resource with an unchanged
revision number will not be migrated. You can see the current revision number of a resource in the Revision
parameter in the object editor.

SAP Enable Now Editions

The migration of a workarea depends on your SAP Enable Now Edition and includes the following steps:

 Authoring Edition - Local workareas

1. Backup of the workarea

2. Preparation of the migration

3. Installation of the new Producer version

4. Migration of the workarea

 Consumption Edition - Manager and local workareas

5. Backup of the database and corresponding files

6. Backup of the local workareas

7. Preparation of the migration

8. Checkout of write permissions for the resources by the master author

9. Installation of the new Producer version

10. Upgrade to the new Manager version

11. Migration of the Manager workarea by the master author

12. Migration of the local workareas by the standard authors

Note
After the migration it is not possible to use the workarea in an older Producer version.

Migration of user-created resources

A workarea can include user-created resources for the creation of individual learning content. Typical user-defined
resources are bubble styles, settings or templates.
During the migration, user-created modifications and settings will be kept and converted into the new resource
structure. The adaptations won’t be deleted.
In a workarea with an up-to-date resource structure imported resources have to be migrated individually.

SAP Enable Now On-Premise Edition

Migrating a Workarea CUSTOMER
3
Migration of an Instant Producer workarea

The workarea migration of an Instant Producer for the Authoring Edition is executed automatically after the first
start of the program.
The workarea migration of an Instant Producer for the Consumption Edition can be done after the migration of
the resources in the Manager workarea (see chapter Manager Workarea). The synchronization is executed
automatically after the first start of the program.

4.1 Local Workarea

The migration of a local workarea of the Authoring Edition allows you to update a local workarea of your Producer.

Preparation for the migration

Before migrating a workarea the following preparations and requirements are necessary:

 Backup workareas
Before migrating a workarea make an archive, which you can revert to in the event of any problems. This can
be done with the Export Archive... function in the menu Workarea -> Administration.

Migration of the workarea

The migration of a workarea can be executed as follows:

1. Install the new Producer version.

2. Open the Producer.

3. Open the workarea by selecting Workarea -> Select Workarea...

4. A dialog box is opened.

○ Select Migrate Workarea to migrate workarea with recommended settings.

○ Select Show Details.

Afterwards the workarea migration dialog box opens. The dialog box shows the recommended
migration action for each available resource group.

Adapt the resource actions using the dropdown box.

It is recommended that you keep the settings. Adaptations are only necessary in a few situations, if
no changes should be made.
For further information on the settings see the chapter Migration Dialog Box.

Select Migrate Workarea to start the migration.

5. The migration will now be executed.

6. Select OK in the progress dialog box, if the migration is completed.

7. With the finishing of the migration a folder with log files opens.
The folder contains archives with the changed and removed resources, as well as log information. The folder is
located in the workarea folder.
8. Select Restart in the dialog box. Restarting the Producer is necessary so that the new resources
and configurations can take effect.
 Note
Do not import the outdated resources of the log folder into your workarea again.

4.2 Manager Workarea

When updating the workarea in an authoring environment with a Manager workarea and a
number of local workareas, it is necessary that the master author performs the update in
one local workarea and afterwards deploys it to the other local workareas. This achieves
a consistent use of the needed resources.

Preparation for the migration

Before migrating a Manager workarea the following preparations and requirements are necessary:

Caution
Make sure, that the preparations and requirements are fulfilled before you perform the migration. This is necessary to avoid errors
during the migration process as well as in the migrated workarea.

 Backup Manager workareas and local workareas

Before migrating a workarea make an archive, which you can revert to in the event of
any problems. This should be done for the Manager workarea on the Manager as well
as for the local workareas of the authors.
 Save write permissions centrally
Save all write permissions of the resources to the server. The write permissions are
necessary for the master author to migrate the resources. This can be done by
selecting a resource and selecting Finish editing.

Migration steps for the master author

The migration can be executed by the master author as follows:

Steps in old Producer and Manager version

1. Open the workarea in the old Producer version.

2. Open the workarea by selecting Workarea -> Select Workarea...

If the authentication dialog box appears, insert your user data with the new password.

3. Start editing resources to get all write permissions. Select the Resources tree and
select Manager Workarea -> Start editing all objects...
4. Close the Producer.

5. Select Shut down in the opened dialog box. Do not return the write permissions.

6. In Manager delete all resources from the trash do avoid the restore of the objects.

Steps in new Producer and Manager version

1. Upgrade the Manager to the new version.

2. Install the new Producer version.

3. Open the Producer.

4. Open the workarea by selecting Workarea -> Select Workarea...