One of the housekeeping tasks I generally perform in the instances I use to develop actual applications is to upgrade the Web IDE. Not only because some minor bugs are swept away, but also because there’s always some additional functionality that makes development easier.
You would generally need access to the marketplace and a proper license for this. However, the engineering team has made this patch available for download in the download manager in revision 23. If the following rings a bell, you might want to give this a try:
“Request failed: Gateway Timeout URI: /che/runner/workspace”
The upgrade process is pretty similar as with any other MTA upgrade, only that this time it is easier because you can download it straight into the instance using the console-based download manager.
Using a Virtual Machine? Add 1GB more RAM to the default, it will need it during the installation process.
These steps apply to revision 23 of HANA express (HANA 2.0, SPS02). You can still go ninja mode and upgrade your MTAs but you will need to perform some manual work and checks (outlined below).
You would generally need access to the marketplace and a proper license for this. However, the engineering team has made this patch available for download in the download manager in revision 23. If the following rings a bell, you might want to give this a try:
“Request failed: Gateway Timeout URI: /che/runner/workspace”
The upgrade process is pretty similar as with any other MTA upgrade, only that this time it is easier because you can download it straight into the instance using the console-based download manager.
Using a Virtual Machine? Add 1GB more RAM to the default, it will need it during the installation process.
Check your version
These steps apply to revision 23 of HANA express (HANA 2.0, SPS02). You can still go ninja mode and upgrade your MTAs but you will need to perform some manual work and checks (outlined below).
If you do not have that version, it means you need to go into the marketplace and look for SAP HANA RUNTIME TOOLS 2.0 and SAP WEB IDE 2 in the software downloads.
You also need the *.mtaext file in this note. The one oyu get from the note has some differnt parameters than what HXE uses. I would recommend you use the file you already have from the original installation as a reference. Command sudo find / -name *mtaext should find the original file.
Whlle you are there, make sure you have the compatible versions of the other MTAs. The command to know what your MTA versions are is xs mtas.
Once you have all of the necessary packages, upload them into your instance and jump to “Upgrade time” below.
Download the patch
Don’t you just love the console-mode download manager? Use it to download the patch straight into the same lucky server that is getting the upgrade.
Login to the xs CLI if you have not already and check the versions of your MTAs while you are there:
xs-admin-login
xs t -s SAP
xs mtas
Now list the packages available for download:
cd /usr/sap/HXE/home/bin
./HXEDownloadManager_linux.bin -X
You need to pay attention here. The Download manager will offer packages for different platforms. In my case, I am using a launcher instance on Google Cloud Platform. The linuxx86_64 version applies here (there is no difference between the VM or Binary method for this particular component), it is the platform what will cause you trouble. Use linuxppc64le if applicable.
./HXEDownloadManager_linux.bin <<check your platform>> installer webide_patch.tgz
Install the upgrade
For the second time, we are going to make sure you are on the right space (SAP) after extracting the files:
tar -xvzf /usr/sap/HXE/home/Downloads/webide_patch.tgz
xs t -s SAP
You might want to give some more room to the backend processes. I have found that life flows more swiftly if you allocate more RAM to the backend processes for Web IDE. These are di-core and di-runner. In previous versions they could even crash and throw an awful
Request failed: Bad Gateway URI: /che/project/workspacee…..
And some other unhandled technical errors.
This randomly would happen after running node.js modules, Fiori wizards and syncing Git repositories. The problem is that this will make these processes take up more memory, which may mean less memory for the rest of the processes. This should not be a problem in cloud environments and I have already pushed the RAM up to 32 GB, so here I go:
Once we are ready, let the installation begin:
xs install ./HANA_EXPRESS_20/DATA_UNITS/XSAC_SAP_WEB_IDE_20/sap-xsac-devx-4.2.31.zip -e ./HANA_EXPRESS_20/DATA_UNITS/XSAC_SAP_WEB_IDE_20/sap-xsac-devx-4.2.31-hxe.mtaext
If you have manually downloaded the runtime tools package, you can install it too with:
xs install XSACHRTT0<<the version you downloaded>>.ZIP
Go get some coffee, pet your cat or dog or dedicate some minutes to mindful meditation. This will take some minutes. The success message will appear when ready:
And command xs mtas will confirm the upgrade has been successful.
Re-run the space enablement tool
Go into the space enablement tool (https://hxehost:51024 – or whatever xs a | grep space says) and redeploy the development space to update the di-builder:
You are all set now.
No comments:
Post a Comment