Symptom
This
note contains information about SAP HANA Application Lifecycle
Management (HALM) for SAP HANA SPS 10, including its restrictions.
Other Terms
HANA, Delivery Unit, XSEngine, Product, Change Recording, CTS Export, CTS+, Installation, Assembly, HALM, Change Management
Reason and Prerequisites
Solution
What´s New in SAP HANA Application Lifecycle Management (HALM) SPS 10
For an overview of the new and changed functions, see SAP HANA Application Lifecycle Management (New and Changed) in the What´s New in the SAP HANA Platform (Release Notes) in the SAP HANA documentation on SAP Help Portal.
What´s New in HALM with SAP HANA SPS 10 Database Maintenance Revision 102.01
As of SAP HANA SPS 10 Database Maintenance Revision 102.01, the SAP HANA Application Lifecycle Management XS application contains an SAP Fiori user interface for installing and updating SAP HANA products and software components. To start it, choose the INSTALLATION tab or the Installation tile on the HALM home screen. You can use it alongside the hdbalm commandline tool. For more information about the usage, see the attachment InstallProdSCV.pdf to this SAP Note.
HALM SPS 10 Restrictions
Browser Support
If you run the SAP HANA Application Lifecycle Management SPS10 in Microsoft Internet Explorer, the Web browser’s back navigation is not supported. This issue does not affect other Web browsers, for example, Mozilla Firefox, Google Chrome or Apple Safari.
The Dependency Viewer in the Delivery Units tab is not supported in Microsoft Internet Explorer.
Transport of Deleted Packages and Delivery Units
Deletions of packages or deletions of objects of deleted packages can only be transported with the transport of complete delivery units. If you delete a package in the source system, you need to use the transport mode Complete Delivery Unit (or All Changelists, if change recording is enabled and you use native SAP HANA transport) to transport object deletions.
This restriction applies to native SAP HANA transport as well as CTS transport.
Integration of SAP HANA Application Lifecycle Management in SAP HANA Studio
On Linux, the integration of SAP HANA Application Lifecycle Management in SAP HANA studio does not work. In this case, HALM has to be called directly in the Web browser using one of the following URLs:
The change recording function in SAP HANA Application Lifecycle Management, which was introduced with HANA SPS 07, has the following restrictions:
Change and Transport System (CTS) Transport
When CTS transport is enabled in one system, any transport route with this system defined as source system or target system is no longer available for native SAP HANA transport. We recommend that you switch the entire SAP HANA transport landscape either to CTS export or to native SAP HANA transport, but not to use both modes in one landscape.
CTS upload by default has 100MB size limit for single file. If you need to export a single archive that exceeds 100 MB, you need to change the icm/HTTP/max_request_size_KB setting in the ABAP server that hosts the Export Web Service.
Command line tool (hdbalm)
For large delivery units, import, export, and transport operations can fail for one of the following reasons:
You can set the value for the "maximum request runtime" parameter in the xsengine.ini file. The value for the following parameter must be set in seconds:
xsengine.ini > httpserver > max_request_runtime
For long running operations, extend the value defined for the default limit for session timeouts. The value for the following parameter must be set in seconds:
xsengine.ini > httpserver > sessiontimeout
You can set the value for the memory settings in the JavaScript virtual machine (jsvm) section of the xsengine.ini:
xsengine.ini > jsvm > max_runtime_bytes
Note that if the XS engine is configured to run in "embedded" mode, the JavaScript virtual machine settings must be configured in the indexserver.ini section. The value for the following parameter must be set in bytes:
indexserver.ini > jsvm > max_runtime_bytes
Target System Restriction
When creating a transport route, the target system for the transport operation is currently tied to the local system by default. This means that you can only transport content from a remote (target) system into a local system. This restriction was introduced to avoid inconsistencies in the system landscape.
Other Restrictions
HALM documentation can be found at the following places:
For an overview of the new and changed functions, see SAP HANA Application Lifecycle Management (New and Changed) in the What´s New in the SAP HANA Platform (Release Notes) in the SAP HANA documentation on SAP Help Portal.
What´s New in HALM with SAP HANA SPS 10 Database Maintenance Revision 102.01
As of SAP HANA SPS 10 Database Maintenance Revision 102.01, the SAP HANA Application Lifecycle Management XS application contains an SAP Fiori user interface for installing and updating SAP HANA products and software components. To start it, choose the INSTALLATION tab or the Installation tile on the HALM home screen. You can use it alongside the hdbalm commandline tool. For more information about the usage, see the attachment InstallProdSCV.pdf to this SAP Note.
HALM SPS 10 Restrictions
Browser Support
If you run the SAP HANA Application Lifecycle Management SPS10 in Microsoft Internet Explorer, the Web browser’s back navigation is not supported. This issue does not affect other Web browsers, for example, Mozilla Firefox, Google Chrome or Apple Safari.
The Dependency Viewer in the Delivery Units tab is not supported in Microsoft Internet Explorer.
Transport of Deleted Packages and Delivery Units
Deletions of packages or deletions of objects of deleted packages can only be transported with the transport of complete delivery units. If you delete a package in the source system, you need to use the transport mode Complete Delivery Unit (or All Changelists, if change recording is enabled and you use native SAP HANA transport) to transport object deletions.
This restriction applies to native SAP HANA transport as well as CTS transport.
Integration of SAP HANA Application Lifecycle Management in SAP HANA Studio
On Linux, the integration of SAP HANA Application Lifecycle Management in SAP HANA studio does not work. In this case, HALM has to be called directly in the Web browser using one of the following URLs:
- HALM Home Screen: http://<WebServerHost>:80<SAPHANAinstance>/sap/hana/xs/lm
- Transport: http://<WebServerHost>:80<SAPHANAinstance>/sap/hana/xs/lm/?page=TransportTab
- Delivery Units: http://<WebServerHost>:80<SAPHANAinstance>/sap/hana/xs/lm/?page=DUManagementTab
- Products: http://<WebServerHost>:80<SAPHANAinstance>/sap/hana/xs/lm/?page=productManagementTab
The change recording function in SAP HANA Application Lifecycle Management, which was introduced with HANA SPS 07, has the following restrictions:
- Change recording requires enough JSVM memory to handle changelists,
for example, search for changes and export/transport changelists and
enable/disable change tracking. If you have received a 500 Internal Server Error
in the browser console and the xsengine_* trace file is out of memory,
then enhance the memory configuration to a proper value. The following
example provides information about how to do this.
xsengine.ini > jsvm > max_runtime_bytes - When you enable change recording, there is no automatic refresh for the Change Manager View and change dialog in SAP HANA studio during the activation process. To refresh the view, you must close and reopen the Change Manager view (or the SAP HANA studio) in order to work in change recording mode.
- The following restrictions apply when creating objects:
- The HTTP destination object created when you register a system with SAP HANA Application Lifecycle Management must be released manually in SAP HANA studio.
- We recommend that you use one delivery unit per changelist, and that you do not add objects that are from other delivery units or not part of any delivery unit.
- Do not use change recording in SAP HANA systems which are also used for ABAP on HANA systems where one of the transport mechanisms SAP HANA Transport for ABAP (HTA) or SAP HANA Transport Container (HTC) is used. Otherwise, import errors can occur.
Change and Transport System (CTS) Transport
When CTS transport is enabled in one system, any transport route with this system defined as source system or target system is no longer available for native SAP HANA transport. We recommend that you switch the entire SAP HANA transport landscape either to CTS export or to native SAP HANA transport, but not to use both modes in one landscape.
CTS upload by default has 100MB size limit for single file. If you need to export a single archive that exceeds 100 MB, you need to change the icm/HTTP/max_request_size_KB setting in the ABAP server that hosts the Export Web Service.
Command line tool (hdbalm)
- If you get one of the following error messages during the installation of an SAP HANA add-on (SAP HANA content) using hdbalm, see SAP Note 2212387 for information about how to solve the error:
- 'Delivery unit <XY> has missing dependencies. Install the required delivery units from content provider.' 'See dependencies error information in the log.'
- 'The product <X> [instance <Y>], has missing dependencies. Check product installation prerequisites' 'See dependencies error information in the log.'
- The command line tool hdbalm does not support the use case where
Maintainance Optimizer (MOPZ) generates a stack.xml and downloads all
software component versions (SCVs) necessary for installation in one directory. hdbalm cannot install all SCVs of this directory at once.
As a workaround, you can use hdbalm to install all SCVs that are relevant for the system with one hdbalm call: hdablm install scv1.zip scv2.zip ….You can use the stack.xml to find out which SCVs are relevant for the system. The SCVs that contain the entry <runtime-type>HDB</runtime-type> can be installed using hdbalm. Afterwards, you have to use the hdbalm register command to register the product information: Hdbalm register <stack.xml>. However, there is the following restriction: Stack.xml files that describe more than one support package stack are not supported. - The warning message "From product version comparison, you have already installed the same product version" displayed during installation of products with caption "SAP HANA PLATFORM EDIT. 1.0" can be ignored.
-
The following error may occur when you use hdbalm with Python version 2.7.9:
CertificateError: hostname '<hostname>' doesn't match either of '<hostname>', '<hostname>'The reason is that there is an bug in Python version 2.7.9. We recommend not to use Python version 2.7.9 with SSL.
- The command line client does not support the transport based on transport routes of type Selected Changelists. hdbalm always transports all active objects of a DU that are part of released changelists, because hdbalm cannot ask for a selection of changelists to be transported.
For large delivery units, import, export, and transport operations can fail for one of the following reasons:
- The time for the operation reaches the maximum limit defined for request runtime.
- The allocated memory reaches the memory limit defined for the JavaScript virtual machine.
You can set the value for the "maximum request runtime" parameter in the xsengine.ini file. The value for the following parameter must be set in seconds:
xsengine.ini > httpserver > max_request_runtime
For long running operations, extend the value defined for the default limit for session timeouts. The value for the following parameter must be set in seconds:
xsengine.ini > httpserver > sessiontimeout
You can set the value for the memory settings in the JavaScript virtual machine (jsvm) section of the xsengine.ini:
xsengine.ini > jsvm > max_runtime_bytes
Note that if the XS engine is configured to run in "embedded" mode, the JavaScript virtual machine settings must be configured in the indexserver.ini section. The value for the following parameter must be set in bytes:
indexserver.ini > jsvm > max_runtime_bytes
Target System Restriction
When creating a transport route, the target system for the transport operation is currently tied to the local system by default. This means that you can only transport content from a remote (target) system into a local system. This restriction was introduced to avoid inconsistencies in the system landscape.
Other Restrictions
- System cluster is supported as of SAP HANA Application Lifecycle Management SPS9, but you would need to use "Solve Inconsistency" on HALM system view to solve system status inconsistencies after cluster configuration changed on the source system.
- The concept of delta transport routes had been further developed into the changelist-based transport routes. During the upgrade from SPS 07 to a higher SPS, all delta routes are converted automatically into routes based on complete delivery units.
HALM documentation can be found at the following places:
- As context-sensitive help in the HALM UI. Use the Help button on the UI to find the correct topic.
- All topics are part of the SAP HANA Application Lifecycle Management Guide
- Tasks that are relevant for developers are described in the SAP HANA Application Lifecyle Management section of the SAP HANA Developer Guide
- Tasks that are relevant for system administrators are described in the SAP HANA Application Lifecyle Management section of the SAP HANA Administration Guide
- If change recording is used, the authorization of the role that is required to move objects between changelists mentioned in the Assign Objects to Changelists topic in the HALM documentation is not sufficient. Instead, the sap.hana.xs.lm.roles::DevelopmentExpert authorization is required for this.
- New document: Deleting SAP HANA Delivery Units and Products, which enhances the SAP HANA Application Lifecycle Management Guide, is attached to this note.
- New with SAP HANA SPS 10 Database Maintenance Revision 102.01: The document InstallProdSCV.pdf about how to use the SAP Fiori UI to install and update SAP HANA products and software components enhances the SAP HANA Application Lifecycle Management SPS 10 documentation. See also: What´s New in HALM with SAP HANA SPS 10 Database Maintenance Revision 102.01.
- Topic: hdbalm Commands, Options, and Variables
Examples for Setting Environment Variables in hdbalm:
On Microsoft Windows, you can set the environment variable for the user as in the following example:
"set HDBALM_USER=<user name>"
On Unix (bourne shell), you can set the environment variable for the user as in the following example:
"export HDBALM_USER=<user name>" - Topic: Enable SSL for hdbalm:
- To make sure that hdbalm uses the correct Python version, set the
environment variable PYTHON_HOME to the location of the correct Python
installation.
On Windows, you can set the environment variable as in the following example:
"set PYTHON_HOME="c:\Program Files\Python27""
On Unix (bourne shell), you can set the environment variable as in the following example:
"export PYTHON_HOME=/usr/python27" - If you use proxies for communication, the proxy settings might also be relevant when you enable SSL. For more information, see Proxy Support for hdbalm.
- Topic: Proxy Support for hdbalm:
On Linux, the environment variables are usually already configured by your system administration. If not, you can set them as in the following example:
"export http_proxy=http://host:port/
export https_proxy=http://host:port/
export no_proxy=.mycompany.com"
On Microsoft Windows, you can set them as described in the following example:
"set http_proxy=http://host:port/
set https_proxy=http://host:port/
set no_proxy=.mycompany.com"
Header Data
| Released On | 18.12.2015 12:38:43 |
| Release Status | Released for Customer |
| Component | HAN-LM-APP SAP HANA Application Lifecycle Management |
| Priority | Recommendations / Additional Info |
| Category | Release planning information |
No comments:
Post a Comment