Skip to Content
Technical Articles

INSTALLATION OF SAP ENABLE NOW MANAGER ON SQL SERVER

Overview

 

The SAP Enable Now Manager serves as a central content management and collaboration platform, simplifying the teamwork of authors. Additionally, it is possible to publish content for specific target groups depending on roles and users as well as measuring the success of the training.

The Manager is a Server Application which runs on the Apache Tomcat Application Server with writing data to a database server and to a server sided file storage. Due to these dependencies, the installation of the Manager needs third-party applications to be installed in advance.

 

Identification

System Requirements

The following minimum hardware configuration is required for running the application server.

Dependencies

The package has dependencies:

 

A. DOWNLOAD JAVA RUN TIME from the below link. And Install it.

https://www.oracle.com/java/technologies/javase-downloads.html

B. DOWNLOAD MICROSOFT VISUAL C++ Package for VS 2013 from below link. And Install it.

https://www.microsoft.com/en-us/download/details.aspx?id=40784

C. Apache Tomcat Installation will be covered in the Installation Process Steps.

D. If your Operating System don’t have an inbuilt SQL Server, then use the below link to install SQL Server.

https://www.tutorialspoint.com/ms_sql_server/ms_sql_server_installation.htm

 

INSTALLATION PROCESS BEGINS

Process Steps

 

Step1 : Select the Operating System as per the System Requirements.

Step 2 : Download the SAP ENABLE NOW MANAGER files from the package CONSUMPTION EDITION 1.0 shown as below.

  • Select the below Version.

 

  • Under this zip file, you will get a “.war” file which is the file we are looking for. And this is the main component of SAP ENABLE NOW, named as MANAGER. In our case, we are taking Microsoft Edition i.e. Manager on SQL.

Step 3: In order to deploy this “WAR file”, we need Apache Tomcat which you can download from the below link.

Apache Tomcat:- https://archive.apache.org/dist/tomcat/tomcat-8/v8.5.11/bin/

  • Select the file as marked below.

Step 4: Next Step is to install apache-tomcat-8.5.11.exe and configure it.

  • Run as administrator and follow the steps below.

Configuration

Set Tomcat service startup to Automatic from default.

Step 5: Change the file size in Apache Tomcat before deploying the WAR file.

  • Find the webapps folder in the Tomcat installation directory.
  • Open manager.
  • Open WEB-INF.
  • Open the file web.xml in your favorite text editor application.
  • Change the value for <max-file-size> and following parameter <max-request-size> from current 52428800 (50MB in Byte) to a higher value fitting the installer size at minimum, e.g. 167772160 (160MB).
  • Save the file and close it.

 

Step 6: Now, we need to deploy the WAR file through Apache Tomcat. Follow the process below.

 

  • Sign in with credentials you mentioned while installing Apache Tomcat.

  •  Click Browse, Select the WAR file and Deploy.

  •  Now you get the Path in the list of applications. Open the Path.

  • Open this link, it will ask for the Credentials. Now, the tricky part is finding out its credentials. You will get it here.

This PC–> Windows(C)–>Program Files–>Apache Software Foundation–>Tomcat 8.5–>webapss–>manager-Microsoft-Edition-10.4.4–>WEB-INF–>classes

 

  •  Under directory classes, you will get config.properties (Get your Credentials from here).

 

Step 7: After Signing in, you are about to configure your SAP Enable Now Manager.

 

  • Fill the required details as below.

  •   Create a new database and select database path. Click Next Steps.

  •  Fill the required details to set E-mail Notifications.

  •  Fill Super Admin details.

 

Initial Workarea

Specify the display name* which will be shown in initial arranged Workarea. You should define a clear allocable short variant of that name, without spaces, in the field Workarea ID*, for example wa for Workarea.Specify the name of the root group in initial arranged Workarea by entering the field Root Group (Display Name)*.

 

Initial Configuration

In field SSO Keytab Files Folder enter the path to your local storage where keytab files, as needed for single sign-on, shall be stored. You can enter or edit this settings later in the server settings.

  •  In step Install Content you get the opportunity to upload predefined sceneries to the Manager. This functionality is for development and testing purposes only. Please click Next step to proceed with the installation process.

  • The window Finished informs you about completion of the install process.

SUPER ADMIN LOGIN

HOME PAGE

INSTALLATION PROCESS AND CONFIGURATION IS DONE NOW.

 

IN CASE, YOU NEED MORE UNDERSTANDING TO THE PROCESS. YOU HAVE ALREADY DOWNLOADED THE MASTER GUIDE FOR IT. YOU CAN FIND AS BELOW.

  • For other configuration in Tomcat like performance optimization or change of port, you can refer this guide.

STARTING AND STOPPING OF MANAGER AND ITS DATABASE

  • START SQL SERVER

  • START APACHE TOMCAT

Conclusion

SAP Enable Now Manager is successfully installed. Now, you can manage your Work areas through its Desktop Components- Producer & Instant Producer. You can find the setup files for these in the Downloaded Folder. Make sure, you have Microsoft Office installed which is a prerequisite for these Desktop Components.

I have come to the end of this Blog Post. Hope this will be beneficial for you. You can also share your comments or feedbacks.

 

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Good article in overall, but here are some inputs from my side:

    1) Instead of Oracle JRE customers can use SAP Machine – this is an open-source JRE, maintained by SAP. Because Oracle changed Java licensing rules in 2018, using SAP Machine will be beneficial.

    2) Apache Tomcat 9.0.31 is recommended as it has fixes for Apache Tomcat vulnerabilities.

    3)You should rename SAP Enable snow Manager .war file prior deploying it. Make is simple and lowercase (Apache Tomcat is case sensitive) like “enmanager“ instead of “manager-Microsoft-edition…bla-bla-bla”

    4) Change the standard Apache Tomcat shutdown port and create a password for the shutdown command.

    Best Regards.

    Anton Mavrin

    SAP Enable Now Senior Consultant at SAP NA