SAP Web IDE for SAP HANA SPS 12

Known Issues
This list provides a set of currently known issues of the SAP Web IDE for SAP HANA development tools
(as of January 2017).

Contents
Development....................................................................................................................................... 1
Building, Running, Packaging, Deploying MTAs .................................................................................... 2
General ............................................................................................................................................... 3
Version Control (Git) ............................................................................................................................ 5
SAP HANA Runtime Tools (HRTT) ......................................................................................................... 5
Security ............................................................................................................................................... 6
Resolved Issues.................................................................................................................................... 7

Development
Topic Issue Impact/Workaround
Debugging Changes in the source require a The Node.js debugger always needs to be restarted
restart of the Node.js debugger. upon any source changes, there is no hot deployment.

Node.js Node.js modules with the XSJS Workaround: To be able to build and run such
development support, which had been created in modules, you need to update their package.json file
the SPS11 version of SAP Web IDE, with the dependencies for the following modules:
cannot be built and run. They "sap-xsjs-test": “1.2.2“
require a manual adjustment after “sap-xsjs”: ”1.6.4”
an upgrade to the SPS12 version. “sap-xsjs-test”: “1.0.7”
SQL Script No embedded support of SQL Workaround: SQL Script debugging can only be
debugging Script debugging. triggered from SAP HANA Runtime Tools application.
Building, Running, Packaging, Deploying MTAs
Topic Issue Impact, Workaround
Selective build It is not possible to build individual As the build of HDB modules is transactional,
database artefacts in HDB modules. in case of error during deployment of all the
artefacts in a module, the deployment process
is completely rolled back.
Workaround: To exclude from build the
artefacts that cause errors, temporarily
change their file extensions to .txt.
MTA No support for module parameters When running a module, the default
application parameters such as host, port,
memory etc., will be used. There is no
workaround.
Deployment It is not possible to deploy a packaged Deploy using the XS Advanced command xs
application (mtar) into SAP HANA XS, deploy.
advanced model (XS Advanced) directly
from SAP Web IDE.
Packaging The package.json that is generated by SAP Though this behavior is required in
Web IDE for an HDB module during development systems, it might be not
packaging always contains the required in QA or production systems.
“autoUndeploy” flag. With this flag, the XS
Advanced HDI deployer automatically Workaround: If this behavior is not required in
undeploys any runtime object that is not the target system in which you deploy the
described in the design-time artifacts. For MTA archive produced by SAP Web IDE, you
example, if an existing table was deleted can manually delete this flag from the
from a CDS file, this table will be package.json of each HDB module in the
automatically deleted from the database archive.
once the CDS is deployed again with the
autoUndeploy flag.
Build/Run After upgrading to SPS12.1, to enable No workaround
building and running modules in existing
projects, you must select a space for each
project in the Project Settings.
Build/Run In the SAP Web IDE View menu, choose Show
Hidden Files. Then check your node.is
After upgrading to SPS12.1 your project’s module’s .che/project.json file to ensure that
node module finds no space the "builders" and "runners" sections
have empty "configs" entries, for example:

"builders": {
"default": "sap.nodejs",
"configs": {
}
},
"runners": {
"default":
system:/sap.nodejs/default",
"configs": {
Topic Issue Impact, Workaround
}
},
Leave the rest unchanged.
Build/Run Currently, some of the Node.js modules in Check whether or not you have Node.js 6.*
the xs_javascript library are not compatible installed on your SAP HANA XS Advanced by
with Node.js 6.*. logging on to XS Advanced and running the xs
runtimes command.
If Node.js 6.* was installed on SAP HANA XS
Advanced before the installation of the 1. If node6.* is listed, locate the
builder component, SAP Web IDE will not associated id value, and run the
be able to build or run some Node.js command xs delete-runtime -i
modules that rely on this library. <node6.* id>
2. Re-enable the builders in your spaces
using the Space Enablement tool.

General
Topic Issue Impact, Workaround
Resource Automatic provisioning of Workaround: To develop an application that uses
provisioning resources, which are declared in resources of other types, such as UAA, manually
the MTA descriptor (mta.yaml), is create the corresponding XS Advanced service using
available only for the the XS Advanced CLI (Command Line Interface), and
com.sap.xs.hdi-container type. add to the mta.yaml a resource with the same name
as the service. Define the required dependencies on
this resource. When the module is run, the specified
resource will be bound to the module.
Service HDI services, which are bound to a For example, a Node.js module has a dependency on
binding module, remain bound to the an HDI resource. When the module is run for the first
module after the resource time, it binds to the corresponding HDI service. If the
dependency in mta.yaml is resource name is changed or the resource dependency
changed or removed. is removed in mta.yaml while the module is running,
the previous service binding remains alongside the
new one. This might cause unexpected behavior.
Workaround: after changing a dependency, stop the
running module explicitly, and then run it again.
Resource When a user logs out, or when the Server-side resources remain allocated, and may grow
deallocation user session terminates after a over time.
timeout, the allocated server-side Workaround: Use the XS Advanced command line
resources are not freed up. tools to manually review the status of running
processes and services, and/or kill unnecessary ones.
Multitenant No support for multitenant
database database containers.
containers
Search Search by file name is case- Workaround: use wild cards in the seach text: for
sensitive. example, search for *ile instead of File or file.
Unicode Various limitations (e.g. filenames In the user-defined names, use ASCII only.
support limited to ASCII letter subsets).
Browser SAP Web IDE is not supported on Use another supported browser (Chrome and Firefox
support Internet Explorer and Edge. on Windows, Chrome and Safari on Mac).
Version Control (Git)
Topic Issue/Limitation Impact, Workaround
Creating a It is not possible to execute the The creation of a repository, a branch, and an initial
repository git init command from SAP commit should be done outside of SAP Web IDE.
Web IDE.
User name The user name and email listed for The user cannot change or override this for a specific
and email your commits are the user name project or Git repository.
listed for and email from your SAP HANA
commits system, not the user name and
email from your Git system.
Branch Creation of multiple branches is not Use the master branch for all changes.
management possible.
Git settings Git settings are defaulted during The default settings allow to work with Git in the SAP
cloning, and cannot be changed by Web IDE development scenarios.
the user.
Integration It is not possible to work with When the developer pushes a commit/change, the
with Gerrit Gerrit as a code review system. remote branch is updated without a code review
process forced by Gerrit. Change ID will not be
generated.
The developer must get a permission to push to the
remote branch (Git administration).
Git operations No support for empty Git When you create a new repository, make sure that it
repositories. has at least one commit. On GitHub, you can achieve
this by selecting the "Initialize this repository with a
README" option in the repository creation page.

SAP HANA Runtime Tools (HRTT)

Topic Issue Impact/Workaround
SQL Occurs after the user has chosen to ignore the The SQL Debugger feature requires a
debugging browser warning about using an invalid or untrusted valid and trusted server certificate
certificate, when running HRTT over HTTPS in Firefox for making its connections, therefore
and Mac OS Safari, and sometimes in Google running HRTT over HTTPS requires a
Chrome. When the user applies SQL debugger well-known certificate to be
settings, a warning message is displayed indicating configured in your XS Advanced
that SQL debugging could not be connected to the environment.
currently selected HDI service.
SQL queries Occurs when executing a SELECT statement where Workaround: use unique column
some column names or name aliases are not unique. aliases in a query to ensure that all
The result set will contain result set column names are unique.
wrong values in these columns. For example:
For example, a query SELECT T.column1 AS x1, T.column2
SELECT T.column1 AS x, T.column2 AS x FROM T; AS x2 FROM T;
would return an incorrect result set.
Security
Topic Issue Impact/Workaround
Authorization Any SAP HANA database user can access the SAP No workaround is available.
HANA Runtime Tools application. However, the user
won’t be able to access the database schema
information or modify any database objects without
the required permissions, such as those granted by
the SpaceDeveloper role.
Backup and SAP Web IDE does not support backup and recovery Use a Git repository as a backup.
recovery for workspace content (projects, folders, files).
File upload No automatic virus scan and content validation of Developers should perform a virus
files before upload to SAP Web IDE. scan and content validation of the
Malicious content can be uploaded to SAP Web IDE. files using external tools before
uploading them.
Alternatively, customers could use
a file-based antivirus to scan the
files on the disk.
Resolved Issues
The following issues have been resolved as of SPS12 Patch 6 (January 2017)

Topic Issue / Impact Workaround

Browser support When using SAP Web IDE on Chrome 55 on a hybrid Use another supported browser.
laptop, you might experience unexpected responses
to mouse clicks and other input events.

The following issues have been resolved as of SPS12 Patch 4 and 5 (November 2016)

Topic Issue / Impact Workaround

Installation Not possible to install SAP Web IDE for SAP HANA or
SAP HANA Runtime Tools (HRTT) on SAP HANA
systems where SSL is enabled.
Upgrade Existing projects are not visible after upgrading SAP
Web IDE for SAP HANA to version SPS12 Patch 3
from previous releases.

Run Node.js The "engine" property in the package.json file is

ignored, so the highest installed version of Node.js
runtime in XS Advanced is used.

The following issues have been resolved as of SPS12 Patch 3 (July 2016)

Topic Issue / Impact Workaround

Space isolation SAP Web IDE supports full isolation between the SAP To create an isolated environment,
space in XS Advanced, in which the SAP tools are for example, for different
installed and run, and a development space in which departments, you can install SAP
applications developed in SAP Web IDE are built and Web IDE in a separate instance of
run. XS Advanced for each department.
However, isolation between different development
spaces is not supported. All applications developed
in SAP Web IDE are located in the same
development space.
This means that any authenticated SAP HANA
database user assigned to the SpaceDeveloper role
for the development space has full access to all
applications in this space, and can potentially cause
disruption or misuse of these applications.
For more information about the XS Advanced
security concept, see SAP HANA Security Guide.
 Topic Issue / Impact Workaround
Administration SAP Web IDE does not restrict access to No workaround is available
administration tasks by roles. Any authenticated SAP
HANA database user assigned to
the SpaceDeveloper role for the SAP space can
manage SSL certificates for Git access, as well as
perform any administration tasks, such as deleting
user workspaces, updating npm registry content and
so on.
Authorization SAP Web IDE does not define any specific roles. This No workaround is available
means that any authenticated SAP HANA database
user can access SAP Web IDE, and create and
maintain projects in his own workspace. However,
the user requires the SpaceDeveloper role for the
development space to build or run applications.
Building After upgrading from SPS11 to SPS12, it is not The builder component is not
possible to build an existing project created in automatically installed into the
SPS11. The builder component does not start. development space.

Workaround: create a new dummy

project. This will trigger the builder
installation.

The following issues have been resolved as of SPS12.

Topic Issue / Impact Workaround

Node.js No support for npm repositories and Workaround: Create a node_modules
development dependencies in locations, which issue SSL subfolder in the Node.js module
certificates that are not publicly trusted. folder, and import there the external
packages including their recursive
dependencies. Write the code and run
the modules as usual.
Building an MTA Building a multi-target application does not Workaround: before building the
automatically trigger a build of all its modules. whole application, build all the
modules in the order according to the
dependencies defined in the MTA
descriptor (mta.yaml).
Workspace and SAP Web IDE does not limit access to No workaround
project access workspaces. Any authenticated SAP HANA
database user have full access to the build and
run logs, as well as database tables.
General In the About box, SAP internal mode is displayed Ignore
under the version number.
Topic Issue / Impact Workaround
SAPUI5 No local installation of SAPUI5 is available. Solution in SPS 12: Developers who for
Developers should refer to the online version of security reasons don’t connect their
SAPUI5. client computers to the Internet, can
install a local version of SAPUI5, and
configure their HTML5 modules to
reference this version, using cross-
MTA dependencies.
Installation Installation of the SAP Web IDE components Workaround: Restart the XS Advanced
sometimes fails. Deploy Service by running the
command xs rs deploy-service
in the XS Advanced CLI, and then
reinstall the components.