This article is about setting up active failover for ArangoDB-PHP, the PHP client driver for ArangoDB. It requires ArangoDB-PHP 3.3.2 or higher, and an ArangoDB server version of 3.3.4 or higher.
Active Failover: Basic Setup
Historically, ArangoDB-PHP has been able to connect to a single ArangoDB endpoint, i.e. one combination of IP address and port number. https://goo.gl/niJiEr #DataIntegration #ML
WALLDORF — SAP SE (NYSE: SAP) today announced the release of SAP Asset Strategy and Performance Management to enhance asset intelligence across the digital supply chain.
The new application helps customers define, plan and monitor optimal maintenance strategies for physical assets and monitor performance data across a network of connected assets in real time.
Using SAP Leonardo Internet of Things (IoT) technology, SAP Asset Strategy and Performance Management connects assets and ties asset management into core business functions, such as maintenance management, manufacturing, finance and human resources. It enables criticality assessments and segmentation of assets to help organizations choose a decision framework, such as failure modes and effects analysis (FMEA), for the optimal maintenance strategy for an asset or assets.
“The latest addition to our enterprise asset management suite provides unparalleled insight across connected asset environments, which is crucial for success in the converged, new world of physical and virtual assets,” said Dr. Tanja Rueckert, President, IoT & Digital Supply Chain at SAP. “Asset management is crucial to any IoT and digital supply chain strategy, and with SAP’s holistic suite, both equipment providers and operators can streamline business operations and fully execute on digital transformation strategies.”
SAP Asset Strategy and Performance Management is the latest addition to cloud solutions for asset management from SAP, which include SAP Asset Intelligence Network and SAP Predictive Maintenance and Service. The suite shares the same underlying data and architecture, offering a single easy-to-implement cloud solution tightly integrated to the SAP ERP application and SAP S/4HANA.
SAP Asset Intelligence Network allows customers to maintain digital twins of physical assets and make them available across networks. The digital twins can be managed across the asset lifecycle, including design, manufacture, sale and operations. This streamlines and automates business processes across the organization, reduces cost and time to market, and enables new collaboration.
SAP Asset Strategy and Performance Management works with SAP Predictive Maintenance and Service to provide real-time insight into asset history, performance, condition and cost. Organizations using the solutions can optimize maintenance, define best strategies for capital investment and risk management, improve customer service and avoid costly disruptions.
For more information, visit the SAP News Center. Follow SAP on Twitter at @SAPLeonardo and @sapnews.
Media Contacts:
Jim Dever, +1 (610) 661-2161, james.dever@sap.com, PT
Kathrin Eiermann, +49 6227 767029, simone.kathrin.eiermann@sap.com, CET
Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as “anticipate,” “believe,” “estimate,” “expect,” “forecast,” “intend,” “may,” “plan,” “project,” “predict,” “should” and “will” and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP’s future financial results are discussed more fully in SAP’s filings with the U.S. Securities and Exchange Commission (“SEC”), including SAP’s most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.
© 2018 SAP SE. All rights reserved.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. http://bit.ly/2FoUeWh #SAP #SAPCloud #AI
This is an end-to-end introduction, how to run a swift application on Cloud Foundry stack within SAP Cloud Platform.
Steps
* Prerequisites
* Clone Sample App
* Push Application to SCP – CloudFroundry
* Modify iOS app to connect to CF instance
Prerequisites – Cloud Foundry CLI: https://docs.cloudfoundry.org/cf-cli/install-go-cli.html – CocoaPods: https://guides.cocoapods.org/using/getting-started.html (I recommend to install it in user directory via following bash command: gem install cocoapods –user-install echo ‘export PATH=$PATH:$HOME/.gem/ruby/2.3.0/bin’ – Login to your CF account cf api https://api.cf.sap.hana.ondemand.com cf login Clone Sample App IBM has provided a backend sample app for the popular iOS App “FoodTracker” by Apple. git clone https://github.com/IBM/FoodTrackerBackend.git You can now walk through of the tutorial or directly check out the branch “CompletedFoodTracker”.
Push Application to SCP – CloudFroundry Once the server application successfully runs locally you can push it to you Cloud Foundry instance. Unfortunately, the swift-buildpack in the `manifest.yml` file points to a service, which doesn’t exist in SCP Cloud Foundry environment, yet. Therefor we have to change the buildpack: buildpack: https://github.com/IBM-Swift/swift-buildpack#2.0.10 Which buildpacks are available, can be found out with following command: cf marketplace Modify file .swift-version of the FoodTracker server to meet the version in the buildpack: 4.0.3 Create the file Procfile in Foodserver folder, with following content, that CF knows what should be started after an successful upload: web: FoodServer Now the server application can be pushed to cf push foodserver In the output you’ll see for the routes output, under which URL your app is deployed and reachable. It’s something like: https://foodserversql-xxxxxx-yyyyyy.cfapps.eu10.hana.ondemand.com The route name is created dynamically, see manifest.yml file… Modify iOS app to connect to CF instance To communicate with FoodTracker-server via iOS app just replace the baseURL, used for creation the KituraKit class: guard let client = KituraKit(baseURL: “https://foodserver-xxxxxxx-yyyyyyy.cfapps.eu10.hana.ondemand.com”) see sample code line here In a next blog I’ll show you how to extend this server side Swift app with a real database. http://bit.ly/2Fot3uB #SAP #SAPCloud #AI
This post by SAP Product Security Response Team shares information on Patch Day Security Notes* that are released on second Tuesday of every month and fix vulnerabilities discovered in SAP products. SAP strongly recommends that the customer visits the Support Portal and applies patches on a priority to protect their SAP landscape.
On 13th of February 2018, SAP Security Patch Day saw the release of 11 Security Notes. Additionally, there were 3 updates to previously released security notes.
We would like to inform our customers that two notes (2525222 and 2547431) released on February Patch Day are expected to be topics of discussion in an upcoming security conference in March. Therefore, we wish to remind you to apply the SAP Security Notes on priority.
List of security notes released on the February Patch Day:
Note#
Title
Priority
CVSS
2525222
[CVE-2018-2395] Security vulnerabilities in SAP Internet Graphics Server (IGS)
Related CVE – CVE-2018-2394, CVE-2018-2396, CVE-2018-2391, CVE-2018-2390, CVE-2018-2386, CVE-2018-2385, CVE-2018-2384, CVE-2018-2393, CVE-2018-2392, CVE-2018-2388, CVE-2018-2383, CVE-2018-2389, CVE-2018-2382, CVE-2018-2387
Product – SAP Internet Graphics Server
Versions – 7.20, 7.20EXT, 7.45, 7.49, 7.53 High
8.3
2565622
[CVE-2018-2368] Missing Authentication check in SAP NetWeaver System Landscape Directory
Product – SAP Netweaver System Landscape Directory
Software Component – LM-CORE; Versions – 7.10, 7.11, 7.20, 7.30, 7.31, 7.40 High
8.3
2589129
[CVE-2018-2374] Security vulnerabilities in SAP HANA Extended Application Services, advanced
Related CVE – CVE-2018-2375, CVE-2018-2376, CVE-2018-2379, CVE-2018-2378, CVE-2018-2377, CVE-2018-2372, CVE-2018-2373
Product – SAP HANA Extended Application Services
Version – 1.0 Medium
7.1
2562089
[CVE-2018-2367] Directory Traversal vulnerability in ABAP File Interface
Product – ABAP File Interface
Software Components – SAP BASIS; Versions – from 7.00 to 7.02, from 7.10 to 7.11, 7.30, 7.31, 7.40, from 7.50 to 7.52 Medium
6.6
2547431
[CVE-2018-2380] Directory Traversal vulnerability in Internet Sales
Product – SAP CRM
Version – 7.01, 7.02, 7.30, 7.31, 7.33, 7.54 Medium
6.6
2545842
[CVE-2018-2381] Missing Authorization check in SAP ERP Financials Information System
Products – SAP ERP Financials Information System
Version – 2.0 Medium
6.3
2427949
Update to Security Note released on April 2017 Patch Day:
Incorrect Authorization Checks in SAP ERP Logistics Customer Master and Vendor Master
Product – SAP ERP Logistics
Software Component – SAP_APPL; Versions – 6.00, 6.02, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18
Software Component – SAPSCORE; Version – 1.08
Software Component – S4CORE; Versions – 1.00, 1.01 Medium
6.3
2494184
Update to Security Note released on August 2017 Patch Day:
Cross-Site Request Forgery (CSRF) vulnerability in multiple SAP Sybase products
Product – SAP Sybase
Software Component – SYBASE REPLICATION SERVER; Version – 15.7.1
Software Component – SIQ; Version – 16.0
Software Components – SY_ESP_SERVER, SYBASE_ESP_ADAPTER_FOR_F.I.X., SYBASE_ESP_ADAP_FOR_OPEN_ADAP, SYBASE_ESP_STUDIO, SY_ESP_ADAPTER_NYSE_TECH_MAMA, SY_ESP_ADAP_TIBCO_RENDEZVOUS, SY_ESP_ADAPTER_ADOBE_FLEX, SY_ESP_ADAP_HTTP_OUTBOUND, SY_ESP_ADAP_LOG_FILE_INPUT, SY_ESP_ADD_IN_MICROSOFT_EXCEL, SY_ESP_ADAP_SL_RTVIEW; Version – 5.1
Software Component – SYBASE_ASE_SERVER; Versions – 15.7, 16.0
Software Component – SYBASE_ASE_CE_SERVER; Version – 15.7
Software Component – SYBASE_SQL_ANYWHERE_SERVER; Versions – SQL_16.0, 17.0 Medium
6.3
2547977
[CVE-2018-2365] Cross-Site Scripting (XSS) vulnerability in SAP Netweaver Portal
Product – SAP Netweaver Portal
Software Component – WebDynpro RunTime; Versions – 7.30, 7.31, 7.40, 7.50 Medium
6.1
2560741
[CVE-2018-2371] Cross-Site Scripting (XSS) Vulnerability in SAML 2.0 Service Provider of AS Java
Product – SAP Netweaver Java Web Application
Version – 7.50 Medium
6.1
2541700
[CVE-2018-2364] Cross-Site Scripting (XSS) vulnerability in SAP CRM WebClient UI
Product – SAP CRM WebClient UI
Software Component – SAP CRM WebClient UI; Versions – 7.01, 7.31, 7.46, 7.47, 7.48, 8.00, 8.01
Software Component – S4FND; Version – 1.02 Medium
6.1
2493727
[CVE-2018-2370] Server Side Request Forgery(SSRF) vulnerability in Central Management Console, BI Launchpad and Fiori BI Launchpad
Product – SAP BI Launchpad
Versions – 4.10, from 4.20, from 4.30 Medium
5.8
2408073
Update to Security Note released on September 2017 Patch Day:
Handling of Digitally Signed notes in SAP Note Assistant
Software Component – SAP Notes Assistant; Versions – from 46A to 46D, from 610 to 640, from 7.00 to 7.02, 7.10, 7.11, 7.30, 7.31, 7.40, from 7.50 to 7.52 Medium
5.5
2572940
[CVE-2018-2369] Information Disclosure in authentication function of SAP HANA
Product – SAP HANA
Software Component – HDB; Versions – 1.00, 2.00 Medium
5.3
________________________________________________________________________________
Security Notes vs Vulnerability Types – February 2018
Security Notes vs Priority Distribution (September 2017 – February 2018)**
* Patch Day Security Notes are all notes that appear under the category of “Patch Day Notes” in SAP Support Portal
** Any Patch Day Security Note released after the second Tuesday, will be accounted for in the following SAP Security Patch Day.
Customers who would like to take a look at all Security Notes that are published or updated after the previous Patch Day, see: https://support.sap.com/securitynotes -> All Security Notes -> Filter for notes which have been published after 9th January 2018.
To know more about the security researchers and research companies who have contributed for security patches of this month, visit SAP Product Security Response Acknowledgement Page
Do write to us at secure@sap.com with all your comments and feedback on this blog post.
SAP Product Security Response Team http://bit.ly/2tztLQ6 #SAP #SAPCloud #AI
