Collaborative Open Market to Place Objects at your Service

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Collaborative Open Market to Place Objects at your Service"

Transcription

1 Collaborative Open Market to Place Objects at your Service D4.1.2 Basic implementation of the COMPOSE runtime infrastructure Project Acronym Project Title COMPOSE Project Number Work Package WP4 Infrastructure Development and Prototyping Lead Beneficiary IBM Editor Yacov Manevich IBM Reviewer Alvaro Villalba BSC Reviewer Juan David Parra PASSAU Dissemination Level PU Contractual Delivery Date 30/04/2014 Actual Delivery Date 30/04/2014 Contractual resubmission Delivery Date Actual resubmission Delivery Date Version V1.1 15/01/ /01/2015 D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 1 of 19

2 Abstract The demonstrated run-time is a highly scalable cloud Runtime Environment hosting applications, services, and service objects in the COMPOSE ecosystem. This is a corner stone of the COMPOSE architecture, such that all components are to be architected in a manner that should be deployable by the provided COMPOSE cloud run-time platform. The COMPOSE cloud is responsible for the management of services accessible through the COMPOSE marketplace, including their core functionalities (e.g., search and discovery, assisted composition, etc.). We started our quest by surveying existing technologies and picking up the one most suitable for COMPOSE to use as a starting point. The conclusion was that Cloud Foundry, an open and extensible PaaS technology is the best basis for the COMPOSE run-time. The present prototype is a customization of the Cloud Foundry PaaS cloud to the specific requirements of the IoT world, as manifested by COMPOSE. A Universal Service Broker is introduced which helps incorporating into the OCMPOSE run-time newly developed services. This is demonstrated by the incorporation of the scalable communication infrastructure as a service to the COMPOSE platform. In addition, we demonstrate the manner in which COMPOSE applications are pushed and hosted by the cloud, and the manner in which they bind to the services they need, as well as being able to exchange information between them. Finally, an external application connects to a COMPOSE application and interacts with it to present the COMPOSE application internal data and capabilities. This document aims to accompany the initial prototype of the COMPOSE run-time platform rather than provide a detailed design document of the demonstrated system. A full-fledged detailed design document is scheduled for the end of the project. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 2 of 19

3 Document History Version Date Comments V0.1 16/04/2014 Initial version V0.2 20/04/2014 Integrated universal Service Broker API V0.3 20/04/2014 First version ready for review V0.4 27/04/2014 Updated after internal IBM review V0.5 29/04/2014 Incorporated comments from PASSAU review V0.6 29/04/2014 Incorporated comments from BSC review V1.0 30/04/2014 Final Version V1.1 05/01/2015 Added sub-section on Criteria for selection of technologies, Important features and Fit with the project requirements, at the request of the reviewers D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 3 of 19

4 Table of Contents Abstract... 2 Document History... 3 List of Figures... 5 List of Tables... 5 Acronyms Introduction Criteria for selection of technologies, Important features and Fit with the project requirements Prototype overview - short description Architectural responsibilities and interactions High level design Main functionalities introduced The Universal Service Broker COMPOSE Customized Services Pushing applications and binding to services Data Services The run-time environment: What is being demonstrated External API - for use by 3rd parties Installation & configuration Future directions D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 4 of 19

5 List of Figures Figure 1: COMPOSE components within the cloud platform... 7 Figure 2: The road to an IoT PaaS Figure 3: Demo outline Figure 4: Universal Service Broker Architecture Figure 5: Binding an application using cf commands Figure 6: Binding an application to a service at "push" time List of Tables Table 1: Acronyms table... 6 D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 5 of 19

6 Acronyms Table 1: Acronyms table Acronym COMPOSE API CF IaaS JS JSON JVM PaaS PID REST RMI UAA URL USBB Meaning Application Programming Interface Cloud Foundry Infrastructure as a Service JavaScript JavaScript Object Notation Java virtual Machine Platform as a Service Process ID Representational state transfer Remote Method Invocation User Account and Authentication Universal Service Locator Universal Service Broker Back-end D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 6 of 19

7 1 Introduction The COMPOSE run-time environment provides hosting and management services to all COMPOSE entities. It is a central piece of the COMPOSE architecture and all additional components are constructed to fit within this platform. The COMPOSE run-time is manifested as a customization of the Cloud Foundry (CF) environment to better serve the IoT world. COMPOSE components are created and hosted as CF services or applications. CF Services are state-full and provide general capabilities to CF applications, and are accessible only to CF applications. CF applications on the other hand are stateless, and may be bound to CF services to get additional capabilities, such as storage, communication, and access to the COMPOSE data management component. Figure 1: COMPOSE components within the cloud platform The generic CF environment is enhanced by COMPOSE additional capabilities. In Figure 1 COMPOSE specific additions which are state-full and accessible only to COMPOSE internal entities are denoted as COMPOSE customized services. The COMPOSE additional capabilities which are state-less and should serve external clients as well are denoted as COMPSE internal components. Finally, COMPOSE hosts also user applications, such as the pilots, which can make use of the added COMPOSE specific capabilities. In order to ease the introduction of the various COMPOSE customized services into the platform we have developed a Universal Service Broker, which eases the task of the new D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 7 of 19

8 COMPOSE customized service provider, as well as easing and mainstreaming the life of the platform provider. All COMPOSE components, such as services and service objects, are hosted or exposed via the platform, either as services or as applications. In addition, external developers applications are hosted as well on the COMPOSE platform, and can bind to COMPOSE provided services. Once the general architecture has been agreed upon and the choice was made to make use of Cloud Foundry as the underlying cloud infrastructure the main design choices refer to the proper break-down of all the rest of the COMPOSE components to fit the COMPOSE platform internal architecture. The criteria for making these decisions depends on the accessibility required from the component, since COMPOSE customized services can be accessed only within the platform, while COMPOSE internal components hosted as CF applications can be accessed by external entities. Additional considerations relate to state information, and the amount of management required, namely whether an existing installation is to be used or whether COMPSE should install and manage the component for the provider. 1.1 Criteria for selection of technologies, Important features and Fit with the project requirements This task is about the design and implementation of the run-time component within the overall COMPOSE architecture. This component is designed to host all the platform ingredients developed in COMPOSE. Both internal components, such as data management, service management, and security, as well as user / developer artefacts, such as service objects, and applications. In addition this component supports the overarching goal of COMPOSE which is to ease the task of IoT application developers, while making sure that the resulting platform is scalable. The COMPOSE runtime infrastructure consists of a customization of an open PaaS cloud platform for the IoT domain. COMPOSE has to deal with a large number of connected objects, applications, and users. The natural choice for hosting such an environment is a cloud based environment. In addition, COMPOSE aims to help developers when creating new IoT applications. Thus, the natural choice for COMPOSE is based on a PaaS environment. In a PaaS environment the developer is relieved from most of the systems aspects of deploying and hosting his applications on the cloud, such as monitoring, disaster recovery and deployment / lifecycle aspects. COMPOSE run-time, as an IoT PaaS, proceeds one step further and provides developers with specific services which are required for developing, running, and hosting IoT applications. In addition the COMPOSE run-time provides collaboration services that enable applications to collaborate and application workflows to be deployed based on individual standalone applications. When looking for an existing cloud PaaS to base the COMPOSE run-time upon we were looking for the following criteria: Ease the task of a developer deploying an IoT application; support for popular web based programming languages such as JS; middleware available with the platform, and ease of extending available middleware; IaaS neutral, open, with strong D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 8 of 19

9 governance and a vibrant community. For all the reasons mentioned above we chose Cloud Foundry as the basis for the COMPOSE platform run-time environment. Other platforms we looked at include Amazon, Azure, Google Apps, and Heroku. Moreover we needed an open source platform that can be modified for our purposes, and CF fulfils this criterion as well. Figure 2: The road to an IoT PaaS 1. Within Cloud Foundry there are two major kinds of entities, namely services and applications. COMPOSE components need to be architected accordingly. CF applications provide Web access, but reside on stateless VMs, thus having no permanent file system; their state storage is supported through cloud storage services (such as DB, NoSQL) bound to the applications. On the other hand CF services reside on statefull VMs, but have no direct web access. Only CF application can access these services through the internal cloud binding mechanism. This division fits well with the COMPOSE architecture, and all COMPOSE components were designed to fit this model. The resulting architecture can be seen in Figure 1. Developers interact with the COMPOSE platform via the developers portal, which is external to the cloud, and communicates with the COMPOSE controller. The developers portal is connected to backend components hosted in the cloud that manage the applications created by the developers, while augmenting and extending it to facilitate the consumption of IoT services. The COMPOSE controller is an adaptation layer that resides in front of the CF cloud controller. It delegates most actions to the CF-controller, but also mediates COMPOSE specific actions, like the management of Service Objects, additional COMPOSE Security functions, etc. In addition it also registers every service object and application within the COMPOSE service registry. Related requirements which are met by the current choice include: Scalability Choice of a scalable cloud run-time solution 1 Adapted from Accelerating your Journey to Application Transformation, EMC World 2012 D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 9 of 19

10 Usability - reduce the complexity of writing and deploying IoT applications the developers portal is integrated with the cloud environment and with a click of a button an application is deployed to the cloud. o Ease of development applications created in the Developers portal are not written from scratch but rather use scaffolding and pre-built components. o Autonomous deployment- language support and environment is automatically created by the cloud. Semantic support the run-time platform hosts the service discovery component which serves as the basis for semantics support t throughout the platform. This component is hosted as a service and enables the COMPOSE controller and the developers portal to communicate with it for inserting new information regarding COMPOSE entities, as well as query for available relevant information. This serves as a basis for the recommendation and composition components as well which are served by the cloud run-time. Support the hosting of applications written in popular web programming languages the first language supported by COMPOSE is JavaScript. Provision platform middleware services (e.g. DBMS, NoSQL, Messaging), and enable easy integration of apps with them A plethora of middleware is provided with the COMPOSE platform for applications to bind to them at run-time. Allow platform services to be extended (i.e. add a custom data-store, messaging solution). The COMPOSE platform adds specific IoT related services to the plain vanilla cloud platform, and enables applications to bind to them at run-time. These services include customized data management, service discovery, and security. Be IaaS neutral, i.e. support hosting on multiple cloud IaaS vendors, or on bare metal, to prevent vendor lock-in. Open with a favourable license. Security the COMPOSE run-time provides ample support for an all engulfing security solution: o UAA re/use account and authentication module o Identity management o UAA services for application to - application security o Code analysis before deployment o Custom buildpack for data provenance & security, information flow control D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 10 of 19

11 Monitoring The COMPOSE run-time platform presents its own monitoring infrastructure to collect and disseminate information on all its relevant entities, using built-in cloud monitoring information as well. 2 Prototype overview - short description The prototype demonstrates the various capabilities of the COMPOSE run-time platform. The cover story is an application that detects impending and actual collisions of airplanes. The application marks these on its real-time interactive map, and stores collision events in an internal DB that can be presented to the user as well. An outline can be viewed in Figure 3. Figure 3: Demo outline The following components are highlighted in the COMPOSE run-time demo: Universal Service Broker which is used to easily add customized services to the platform. Customized Services the COMPOSE communication infrastructure is added as a service to the COMPOSE platform. It is introduced by the universal Service Broker, and is being bound by COMPOSE applications using it to communicate information between them. COMPOSE applications being run and hosted by the platform. Bound to standard and COMPOSE specific services. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 11 of 19

12 o Collision detector - Collects sensor coordinates, detects imminent collisions, and publishes collision warnings and sensor coordinates via the COMPOSE communication service. The collision locations are saved in a MySQL database. This application binds to the communication service and to a MySQL DB instance o Demo frontend application - Subscribed to updates from the communication services. Receives requests from the demo applet for sensor coordinates and collision history. This application binds to the same communication service and to a MySQL DB instance o Demo simulator - Performs REST calls to the Service Object API endpoint to update sensor s coordinates that simulate planes locations. External applet that connects to the COMPOSE frontend application and presents the current coordinates on a map, including an indication of near or real collisions. It can also query the COMPOSE frontend application for a history of collisions and presents them to the user. 2.1 Architectural responsibilities and interactions As can be seen in Figure 1 the COMPOSE run-time component lies at the heart of the COMPOSE platform, and all other COMPOSE components need to interact with it. Some of the COMPOSE components will be connected to the platform as COMPOSE specific services, and will be connected via the universal Service Broker. An example of such a component is the COMPOSE communication infrastructure. Some COMPOSE components will be broken down into a back-end component running as a CF service and a front-end component running as a CF application. Examples of this include the COMPOSE data management layer, and the COMPOSE discovery capability. Some components will have to reside and interact with the underlying cloud infrastructure itself. Examples of that include the COMPOSE controller and some of the Security components. Finally some components will be hosted as COMPOSE applications along with external developer provided applications. 2.2 High level design Main functionalities introduced Internally a standard Cloud Foundry installation was enhanced to accommodate COMPOSE specific requirements, which represent IoT requirements in general. These enhancements include a Universal Service Broker to add specific COMPOSE services to the cloud run-time. For this demonstration the scalable communication infrastructure was incorporated as a service to the run-time environment. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 12 of 19

13 2.2.1 The Universal Service Broker The service broker is a mediator between service providers that wish to offer new capabilities to CF applications on the one hand, and Cloud Foundry on the other hand that hosts the applications, and mediates between the applications and the services. In most cases each service provider implements its own service broker, which takes a toll on the service provider and on the cloud foundry environment management team in the form of integration overhead. Since COMPOSE aims to ease the life of developers, customized service providers, and platform managers, we opted for the creation of this Universal Service Broker which is controlled by the platform provider. The COMPOSE run-time cloud based installation comes with a universal service broker preinstalled, which requires from the service provider only a couple of scripts that interact directly with the service provider itself. This solution enables to integrate into the COMPOSE platform cloud any kind of service, while minimizing the demands from the service provider and removing as much customization work as possible. The universal service broker consists of two parts, namely a servlet as the front-end and a backend. The front-end is a thin Tomcat servlet that is stateless, and thus can be hosted as a Cloud Foundry application. The servlet receives the standard REST requests from the Cloud Controller, parses them and forwards them to the Service Broker s backend (USBB) component which is a java application that uses a Derby database as its data store (embedded by default, but can also run as a network server). The servlet communicates with the backend using RMI. The backend receives the request, and executes the relevant script provided by the service provider, then reads the output of the script s execution (whether the execution was successful or failed, etc.) and sends the response back to the servlet, which passes it back to the Cloud Controller. Figure 4: Universal Service Broker Architecture The universal service broker also removes management overhead from the cloud administrator. When a new service is added, it automatically detects this and updates the cloud controller. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 13 of 19

14 It is also very easy to deploy. The front end is a tomcat servlet which is deployed in a standard fashion, and the back end is a native java application that installs its database upon first launch COMPOSE Customized Services The cloud run-time environment comes with two kinds of services: Generic services, such as MySQL database (shared databases and private ones alike), apache Derby database, etc. Custom built services, that are unique to COMPOSE, such as the COMPOSE communication infrastructure, a service that provides easy and scalable communication between applications. The COMPOSE communication service is a highly scalable, light-weight, fully-distributed, network-aware communication middleware that has self-organizing structured overlay properties. It provides publish/subscribe messaging to applications, such that applications don t need to know the host and port of fellow peers, they only need to know the name of the topic\group they send\receive the information to\from, and the infrastructure takes care of the low level communication tasks such as routing the messages between the peers of the overlay, and forming a fault-tolerant, strongly connected topology. In the current prototype the pub / sub infrastructure is used to communicate events of interest between 2 COMPOSE applications running within the cloud Pushing applications and binding to services When a developer wants to upload an application to the COMPOSE cloud platform, it registers the new application and then uploads the binaries\code and relevant resources the application needs to the Cloud Controller, where the data is saved in a central blob store. This procedure is called pushing an application. After the binaries are uploaded to the COMPOSE run-time, it detects the type of application (ruby, node.js, java, etc.), and installs a matching environment that launches the application (this is called a buildpack ). An application can utilize external software in the form of services. In Cloud Foundry, binding is being done between service instances and applications, and when a user binds an application, the Cloud Controller contacts the appropriate service broker for credentials (host, port, username & password, etc.) and injects the credentials in an environment variable inside the application. This procedure provides the application with the required credentials in order to interact with the service while maintaining data confidentiality Data Services In addition, the current prototype makes use of data services provided by BSC, in the form of a Service Object endpoint to which an application feeds simulated coordinates, and COMPOSE D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 14 of 19

15 applications extract and use that data. The COMPOSE service object endpoint exposes a JSON and REST based API for creating, updating, and obtaining date from service objects The run-time environment: Ubuntu LTS Cloud Foundry build 2222, single instance using bosh_nise MySQL and Service Broker backend running on the same machine, while frontend running as a Cloud Foundry application. Compose Communication service running on 3 Linux blades Cloud Foundry instance managed from a win7 machine with cf-cli installed Service Objects API running in BSC serviced at 3 What is being demonstrated The COMPOSE run-time demo simulates real time coordinates of flying objects like planes, and sends them to the COMPOSE service REST API endpoint. Each sensor has a related Service Object in COMPOSE. The Service object is queried by the collision detector for updated coordinates, and if a collision is detected a record is inserted into a MySQL database. The updated coordinates are passed on to the COMPOSE communication infrastructure, which passes the data to the COMPOSE frontend-demo application. This application caches the updated coordinates and collision history taken from the database, and presents the information to the user. Both the collision detector and the COMPOSE frontend-demo application are hosted as Cloud Foundry applications which are bound to the same service instances (COMPOSE communication and a MySQL database) before their deployment to the cloud. 4 External API - for use by 3rd parties The Universal service broker executes scripts supplied by the service provider and returns their output to the Cloud Controller. For each service, its service configuration file (named like the service name and suffixed with.yml) states where to find the scripts that are executed by the USBB upon provisioning\unprovisioning\bind\unbind requests passed by the servlet (originated from the Cloud Controller). The scripts need to comply with a minimal set of rules: All scripts need to output whether their invocation was successful by outputting the tagged string: <BROKER>result=SUCCESS</BROKER> to standard output. The service broker ignores all output not surrounded by <BROKER> </BROKER> tags. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 15 of 19

16 The provision script also needs to output <BROKER>instanceid=somevalue</BROKER>. This value is the value the service broker uses in order to translate the CF provided unique instance ID to the service provider's instance upon unprovisioning. The bind script needs to output a similar field: <BROKER>bindid=somevalue</BROKER> for the same reason. Besides that, since the bind operation is used to connect the CF application to the new service being provided, the bind operation in CF actually simply sets the VCAP_SERVICES environment variable that contains all of the credentials and connection information an application needs in order to connect to the service. These credentials (if there are any) should be supplied by the bind script, and the service broker simply passes them on to cloud foundry in the bind response. Each credential should be in its own line, for example: <BROKER>username=testuser</BROKER> Every key=value combination whose key is not instanceid or bindid will be passed to the VCAP_SERVICES as a credential. Supported value types are strings and integers only. 4.1 Installation & configuration In order to deploy the backend, simply launch the backend application with the command: java -Dconf.init=true -Djava.rmi.server.hostname=server-ip -jar broker.jar conf.xml &> broker.log with the server s ip address. This automatically creates an embedded derby database instance, a configuration file (conf.xml), a services directory and a template service with a configuration file (test_service.yml). Use this template service to create new services. Upon start-up, the service broker tries to update the Cloud Controller with the services it possesses. After the first launch, the backend configuration file needs to be edited to suit the environment and the backend process needs to be re-run in order to reload the configuration. In order to add a new service all that is needed is simply to create a directory with the same name as the new service (under the main CF services directory) and create the YAML configuration file and the appropriate scripts (and of course- have the scripts listed in the configuration file). There is no need to restart the service broker in order to add new services. It is important to deploy the broker backend first and the servlet only later, since if the servlet starts up and fails to connect to the backend, it won t try again(but will try again if the first attempt of connection since start-up was successful), so make sure the standard output log file has the lines: Connecting to rmi:// :5611/broker Connected, before continuing with further steps. When you re done, it s time to introduce the service broker to the Cloud Controller. This is done by invoking cf add-service-broker and giving it the URL of the servlet (depends on where and how you deployed the Tomcat server). After adding the service broker, you should be able to provision and bind your new services. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 16 of 19

17 Binding applications to a service can be done at application creation time, as can be seen in Figure 5, or after the application has been created, using the cf-bind-service command, as can be seen in Figure 6. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 17 of 19

18 Figure 6: Binding an application to a service at "push" time Figure 5: Binding an application using cf commands D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 18 of 19

19 5 Future directions Incorporation of the COMPOSE controller and service management component into the COMPOSE platform. This will streamline the management of user provided COMPOSE applications within the COMPOSE platform. Deployment of additional services. First and foremost, the data management component. Next in line is the discovery mechanism. Introduction of the COMPOSE security components into the platform. Integration of the COMPOSE pilots to be run within the COMPOSE platform, as a validation point that all necessary capabilities are in place and functioning well. D4.1.2-Basic implementation of the COMPOSE runtime infrastructure Page 19 of 19

Collaborative Open Market to Place Objects at your Service

Collaborative Open Market to Place Objects at your Service Collaborative Open Market to Place Objects at your Service D6.4.1 Marketplace integration First version Project Acronym COMPOSE Project Title Project Number 317862 Work Package WP6 Open marketplace Lead

More information

Collaborative Open Market to Place Objects at your Service

Collaborative Open Market to Place Objects at your Service Collaborative Open Market to Place Objects at your Service D3.2.2.2 Prototype of the service monitoring tools Project Acronym COMPOSE Project Title Project Number 317862 Work Package WP3.2 Services deployment

More information

Assignment # 1 (Cloud Computing Security)

Assignment # 1 (Cloud Computing Security) Assignment # 1 (Cloud Computing Security) Group Members: Abdullah Abid Zeeshan Qaiser M. Umar Hayat Table of Contents Windows Azure Introduction... 4 Windows Azure Services... 4 1. Compute... 4 a) Virtual

More information

APP DEVELOPMENT ON THE CLOUD MADE EASY WITH PAAS

APP DEVELOPMENT ON THE CLOUD MADE EASY WITH PAAS APP DEVELOPMENT ON THE CLOUD MADE EASY WITH PAAS This article looks into the benefits of using the Platform as a Service paradigm to develop applications on the cloud. It also compares a few top PaaS providers

More information

Collaborative Open Market to Place Objects at your Service

Collaborative Open Market to Place Objects at your Service Collaborative Open Market to Place Objects at your Service D5.2.1 Prototype providing identity management and provenance in COMPOSE Project Acronym Project Title COMPOSE Project Number 317862 Work Package

More information

Bluemix: The Open Platform as a Service

Bluemix: The Open Platform as a Service Jia Tan (tanjia@cn.ibm.com) Senior Software Architect IBM China Software Development Lab Apr 2014 Bluemix: The Open Platform as a Service 2013 IBM Corporation New models of product & service innovation

More information

CLOUD TECH SOLUTION AT INTEL INFORMATION TECHNOLOGY ICApp Platform as a Service

CLOUD TECH SOLUTION AT INTEL INFORMATION TECHNOLOGY ICApp Platform as a Service CLOUD TECH SOLUTION AT INTEL INFORMATION TECHNOLOGY ICApp Platform as a Service Open Data Center Alliance, Inc. 3855 SW 153 rd Dr. Beaverton, OR 97003 USA Phone +1 503-619-2368 Fax: +1 503-644-6708 Email:

More information

Platform as a Service and Container Clouds

Platform as a Service and Container Clouds John Rofrano Senior Technical Staff Member, Cloud Automation Services, IBM Research jjr12@nyu.edu or rofrano@us.ibm.com Platform as a Service and Container Clouds using IBM Bluemix and Docker for Cloud

More information

Deploy Your First CF App on Azure with Template and Service Broker. Thomas Shao, Rita Zhang, Bin Xia Microsoft Azure Team

Deploy Your First CF App on Azure with Template and Service Broker. Thomas Shao, Rita Zhang, Bin Xia Microsoft Azure Team Deploy Your First CF App on Azure with Template and Service Broker Thomas Shao, Rita Zhang, Bin Xia Microsoft Azure Team Build, Stage, Deploy, Publish Applications with one Command Supporting Languages

More information

Programming IoT Gateways With macchina.io

Programming IoT Gateways With macchina.io Programming IoT Gateways With macchina.io Günter Obiltschnig Applied Informatics Software Engineering GmbH Maria Elend 143 9182 Maria Elend Austria guenter.obiltschnig@appinf.com This article shows how

More information

Implementing Microsoft Azure Infrastructure Solutions

Implementing Microsoft Azure Infrastructure Solutions Course Code: M20533 Vendor: Microsoft Course Overview Duration: 5 RRP: 2,025 Implementing Microsoft Azure Infrastructure Solutions Overview This course is aimed at experienced IT Professionals who currently

More information

Collaborative Open Market to Place Objects at your Service

Collaborative Open Market to Place Objects at your Service Collaborative Open Market to Place Objects at your Service D6.2.1 Developer SDK First Version D6.2.2 Developer IDE First Version D6.3.1 Cross-platform GUI for end-user Fist Version Project Acronym Project

More information

cf push: Push your Scala/Play apps to Cloud Foundry

cf push: Push your Scala/Play apps to Cloud Foundry cf push: Push your Scala/Play apps to Cloud Foundry RAGHAVAN N. SRINIVAS @ragss 1 Who am I? Rags (not to Riches) and work for EMC CODE Middleware and Application programmer Architect and Evangelist Part

More information

The OpenWhisk Platform. Cloud native Serverless Event driven Microservices

The OpenWhisk Platform. Cloud native Serverless Event driven Microservices The OpenWhisk Platform Cloud native Serverless Event driven Microservices What you will learn today How cloud computing has recently evolved to enable developers to write cloud native applications better,

More information

Migration and Building of Data Centers in IBM SoftLayer with the RackWare Management Module

Migration and Building of Data Centers in IBM SoftLayer with the RackWare Management Module Migration and Building of Data Centers in IBM SoftLayer with the RackWare Management Module June, 2015 WHITE PAPER Contents Advantages of IBM SoftLayer and RackWare Together... 4 Relationship between

More information

Course 20533: Implementing Microsoft Azure Infrastructure Solutions

Course 20533: Implementing Microsoft Azure Infrastructure Solutions Course 20533: Implementing Microsoft Azure Infrastructure Solutions Overview About this course This course is aimed at experienced IT Professionals who currently administer their on-premises infrastructure.

More information

Stackato PaaS Architecture: How it works and why.

Stackato PaaS Architecture: How it works and why. Stackato PaaS Architecture: How it works and why. White Paper Published in 2012 Stackato PaaS Architecture: How it works and why. Stackato is software for creating a private Platform-as-a-Service (PaaS).

More information

Migration and Building of Data Centers in IBM SoftLayer with the RackWare Management Module

Migration and Building of Data Centers in IBM SoftLayer with the RackWare Management Module Migration and Building of Data Centers in IBM SoftLayer with the RackWare Management Module June, 2015 WHITE PAPER Contents Advantages of IBM SoftLayer and RackWare Together... 4 Relationship between

More information

This presentation covers virtual application shared services supplied with IBM Workload Deployer version 3.1.

This presentation covers virtual application shared services supplied with IBM Workload Deployer version 3.1. This presentation covers virtual application shared services supplied with IBM Workload Deployer version 3.1. WD31_VirtualApplicationSharedServices.ppt Page 1 of 29 This presentation covers the shared

More information

Intel IT s Cloud Journey. Speaker: [speaker name], Intel IT

Intel IT s Cloud Journey. Speaker: [speaker name], Intel IT Intel IT s Cloud Journey Speaker: [speaker name], Intel IT Accelerating The Corporate IT Journey Cloud enables ubiquitous access to resources and applications, and workload flexibility Cloud IaaS Infrastructure

More information

TOSCA Interoperability Demonstration

TOSCA Interoperability Demonstration Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard TOSCA Interoperability Demonstration Participating Companies: Join the TOSCA Technical Committee www.oasis-open.org, join@oasis-open.org

More information

AdRadionet to IBM Bluemix Connectivity Quickstart User Guide

AdRadionet to IBM Bluemix Connectivity Quickstart User Guide AdRadionet to IBM Bluemix Connectivity Quickstart User Guide Platform: EV-ADRN-WSN-1Z Evaluation Kit, AdRadionet-to-IBM-Bluemix-Connectivity January 20, 2015 Table of Contents Introduction... 3 Things

More information

IBM Bluemix. The Digital Innovation Platform. Simon Moser (smoser@de.ibm.com) @mosersd

IBM Bluemix. The Digital Innovation Platform. Simon Moser (smoser@de.ibm.com) @mosersd IBM Bluemix The Digital Innovation Platform Simon Moser (smoser@de.ibm.com) @mosersd Who am I? - Senior Technical Staff Member at IBM Research & Development Lab in Böblingen, Germany - Bluemix Application

More information

Open Source Technologies on Microsoft Azure

Open Source Technologies on Microsoft Azure Open Source Technologies on Microsoft Azure A Survey @DChappellAssoc Copyright 2014 Chappell & Associates The Main Idea i Open source technologies are a fundamental part of Microsoft Azure The Big Questions

More information

Exam Name: IBM WebSphere Process Server V6.2,

Exam Name: IBM WebSphere Process Server V6.2, Vendor: IBM Exam Code: 000-375 Exam Name: IBM WebSphere Process Server V6.2, System Administration Version: DEMO 1.A company has an IBM WebSphere Process Server clustered environment running. A system

More information

Windows Azure Pack Installation and Initial Configuration

Windows Azure Pack Installation and Initial Configuration Windows Azure Pack Installation and Initial Configuration Windows Server 2012 R2 Hands-on lab In this lab, you will learn how to install and configure the components of the Windows Azure Pack. To complete

More information

Implementing Microsoft Azure Infrastructure Solutions

Implementing Microsoft Azure Infrastructure Solutions Course 20533: Implementing Microsoft Azure Infrastructure Solutions Course details Course Outline Module 1: Introduction to Azure This module provides the students a high level introduction to Azure. Cloud

More information

JAVA IN THE CLOUD PAAS PLATFORM IN COMPARISON

JAVA IN THE CLOUD PAAS PLATFORM IN COMPARISON JAVA IN THE CLOUD PAAS PLATFORM IN COMPARISON Eberhard Wolff Architecture and Technology Manager adesso AG, Germany 12.10. Agenda A Few Words About Cloud Java and IaaS PaaS Platform as a Service Google

More information

PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者

PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者 PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者 http://www.pass4test.jp 1 年 で 無 料 進 級 することに 提 供 する Exam : C2120-800 Title : IBM PureApplication System V1.1, System Administration Vendor : IBM Version : DEMO 1 / 4

More information

Intel IT Cloud Extending OpenStack* IaaS with Cloud Foundry* PaaS

Intel IT Cloud Extending OpenStack* IaaS with Cloud Foundry* PaaS Intel IT Cloud Extending OpenStack* IaaS with Cloud Foundry* PaaS Speaker: Catherine Spence, IT Principal Engineer, Cloud Computing Acknowledgements: Aaron Huber, Jon Price November 2014 Legal Notices

More information

CARRIOTS TECHNICAL PRESENTATION

CARRIOTS TECHNICAL PRESENTATION CARRIOTS TECHNICAL PRESENTATION Alvaro Everlet, CTO alvaro.everlet@carriots.com @aeverlet Oct 2013 CARRIOTS TECHNICAL PRESENTATION 1. WHAT IS CARRIOTS 2. BUILDING AN IOT PROJECT 3. DEVICES 4. PLATFORM

More information

Implementing Microsoft Azure Infrastructure Solutions 20533B; 5 Days, Instructor-led

Implementing Microsoft Azure Infrastructure Solutions 20533B; 5 Days, Instructor-led Implementing Microsoft Azure Infrastructure Solutions 20533B; 5 Days, Instructor-led Course Description This course is aimed at experienced IT Professionals who currently administer their on-premises infrastructure.

More information

Chris Rosen, Technical Product Manager for IBM Containers, crosen@us.ibm.com Lin Sun, Senior Software Engineer for IBM Containers, linsun@us.ibm.

Chris Rosen, Technical Product Manager for IBM Containers, crosen@us.ibm.com Lin Sun, Senior Software Engineer for IBM Containers, linsun@us.ibm. Chris Rosen, Technical Product Manager for IBM Containers, crosen@us.ibm.com Lin Sun, Senior Software Engineer for IBM Containers, linsun@us.ibm.com Please Note IBM s statements regarding its plans, directions,

More information

WINDOWS AZURE EXECUTION MODELS

WINDOWS AZURE EXECUTION MODELS WINDOWS AZURE EXECUTION MODELS Windows Azure provides three different execution models for running applications: Virtual Machines, Web Sites, and Cloud Services. Each one provides a different set of services,

More information

API Management: Powered by SOA Software Dedicated Cloud

API Management: Powered by SOA Software Dedicated Cloud Software Dedicated Cloud The Challenge Smartphones, mobility and the IoT are changing the way users consume digital information. They re changing the expectations and experience of customers interacting

More information

Course 20533B: Implementing Microsoft Azure Infrastructure Solutions

Course 20533B: Implementing Microsoft Azure Infrastructure Solutions Course 20533B: Implementing Microsoft Azure Infrastructure Solutions Sales 406/256-5700 Support 406/252-4959 Fax 406/256-0201 Evergreen Center North 1501 14 th St West, Suite 201 Billings, MT 59102 Course

More information

zen Platform technical white paper

zen Platform technical white paper zen Platform technical white paper The zen Platform as Strategic Business Platform The increasing use of application servers as standard paradigm for the development of business critical applications meant

More information

Collaborative Open Market to Place Objects at your Service

Collaborative Open Market to Place Objects at your Service Collaborative Open Market to Place Objects at your Service D8.2.3.2 Training actions report Project Acronym Project Title COMPOSE Project Number 317862 Work Package WP8 Dissemination, Training, and Stakeholders

More information

WEBAPP PATTERN FOR APACHE TOMCAT - USER GUIDE

WEBAPP PATTERN FOR APACHE TOMCAT - USER GUIDE WEBAPP PATTERN FOR APACHE TOMCAT - USER GUIDE Contents 1. Pattern Overview... 3 Features 3 Getting started with the Web Application Pattern... 3 Accepting the Web Application Pattern license agreement...

More information

AppStack Technology Overview Model-Driven Application Management for the Cloud

AppStack Technology Overview Model-Driven Application Management for the Cloud AppStack Technology Overview Model-Driven Application Management for the Cloud Accelerating Application Time-to-Market The last several years have seen a rapid adoption for public and private cloud infrastructure

More information

Trusted Analytics Platform (TAP) TAP Technical Brief. October 2015. trustedanalytics.org

Trusted Analytics Platform (TAP) TAP Technical Brief. October 2015. trustedanalytics.org Trusted Analytics Platform (TAP) TAP Technical Brief October 2015 TAP Technical Brief Overview Trusted Analytics Platform (TAP) is open source software, optimized for performance and security, that accelerates

More information

Getting Started Hacking on OpenNebula

Getting Started Hacking on OpenNebula LinuxTag 2013 Berlin, Germany, May 22nd Getting Started Hacking on OpenNebula Carlos Martín Project Engineer Acknowledgments The research leading to these results has received funding from Comunidad de

More information

Setting up your virtual infrastructure using FIWARE Lab Cloud

Setting up your virtual infrastructure using FIWARE Lab Cloud Setting up your virtual infrastructure using FIWARE Lab Cloud Fernando López Telefónica I+D Cloud Architects, FIWARE fernando.lopezaguilar@telefonica.com, @flopezaguilar (Slides: http://tinyurl.com/fiwarelab-cloud)

More information

MS 20533B - Implementing Microsoft Azure Infrastructure Solutions

MS 20533B - Implementing Microsoft Azure Infrastructure Solutions MS 20533B - Implementing Microsoft Azure Infrastructure Solutions COURSE OVERVIEW: This course is aimed at experienced IT Professionals who currently administer their on-premises infrastructure. The course

More information

Cloud Powered Mobile Apps with Azure

Cloud Powered Mobile Apps with Azure Cloud Powered Mobile Apps with Azure Malte Lantin Technical Evanglist Microsoft Azure Agenda Mobile Services Features and Demos Advanced Features Scaling and Pricing 2 What is Mobile Services? Storage

More information

Portable, Interoperable Cloud Applications using TOSCA

Portable, Interoperable Cloud Applications using TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard Portable, Interoperable Cloud Applications using TOSCA Demonstrated using: Vnomic s Service Designer, IBM ISM Cloud Marketplace

More information

Networks and Services

Networks and Services Networks and Services Dr. Mohamed Abdelwahab Saleh IET-Networks, GUC Fall 2015 TOC 1 Infrastructure as a Service 2 Platform as a Service 3 Software as a Service Infrastructure as a Service Definition Infrastructure

More information

DEPLOYMENT GUIDE Version 1.1. Deploying the BIG-IP LTM v10 with Citrix Presentation Server 4.5

DEPLOYMENT GUIDE Version 1.1. Deploying the BIG-IP LTM v10 with Citrix Presentation Server 4.5 DEPLOYMENT GUIDE Version 1.1 Deploying the BIG-IP LTM v10 with Citrix Presentation Server 4.5 Table of Contents Table of Contents Deploying the BIG-IP system v10 with Citrix Presentation Server Prerequisites

More information

The Compatible One Application and Platform Service 1 (COAPS) API User Guide

The Compatible One Application and Platform Service 1 (COAPS) API User Guide The Compatible One Application and Platform Service 1 (COAPS) API User Guide Using the COAPS API (v1.5.3) to provision and manage applications on Cloud Foundry Telecom SudParis, Computer Science Department

More information

Platform Architecture & Integration with OpenShift

Platform Architecture & Integration with OpenShift Platform Architecture & Integration with OpenShift Presenter: Dr Mícheál Ó Foghlú Senior Director Software Engineering DATE: 2015-06-25 TIME: 3:40-4:40 VENUE: Room 302 Agenda What is the Red Hat Mobile

More information

Lunch and Learn: BlueMix to Mainframe making development accessible in the

Lunch and Learn: BlueMix to Mainframe making development accessible in the Lunch and Learn: BlueMix to Mainframe making development accessible in the Cloud Rosalind Radcliffe IBM Distinguished Engineer, IBM Academy of Technology rradclif@us.ibm.com @RosalindRad Insert Custom

More information

Collaborative Open Market to Place Objects at your Service

Collaborative Open Market to Place Objects at your Service Collaborative Open Market to Place Objects at your Service D6.1.1 Functional Requirements and Specification of Open Marketplace Developers API Project Acronym Project Title COMPOSE Project Number 317862

More information

D5.4.4 Integrated SemaGrow Stack API components

D5.4.4 Integrated SemaGrow Stack API components ICT Seventh Framework Programme (ICT FP7) Grant Agreement No: 318497 Data Intensive Techniques to Boost the Real Time Performance of Global Agricultural Data Infrastructures Deliverable Form Project Reference

More information

Towards a common definition and taxonomy of the Internet of Things. Towards a common definition and taxonomy of the Internet of Things...

Towards a common definition and taxonomy of the Internet of Things. Towards a common definition and taxonomy of the Internet of Things... Towards a common definition and taxonomy of the Internet of Things Contents Towards a common definition and taxonomy of the Internet of Things... 1 Introduction... 2 Common characteristics of Internet

More information

Redpaper Axel Buecker Kenny Chow Jenny Wong

Redpaper Axel Buecker Kenny Chow Jenny Wong Redpaper Axel Buecker Kenny Chow Jenny Wong A Guide to Authentication Services in IBM Security Access Manager for Enterprise Single Sign-On Introduction IBM Security Access Manager for Enterprise Single

More information

Interoperability and Portability for Cloud Computing: A Guide

Interoperability and Portability for Cloud Computing: A Guide Interoperability and Portability for Cloud Computing: A Guide November, 2014 Contents Acknowledgements... 3 Motivation and Considerations... 4 Interoperability & Portability Overview... 5 Basic Definition

More information

Team: May15-17 Advisor: Dr. Mitra. Lighthouse Project Plan Client: Workiva Version 2.1

Team: May15-17 Advisor: Dr. Mitra. Lighthouse Project Plan Client: Workiva Version 2.1 Team: May15-17 Advisor: Dr. Mitra Lighthouse Project Plan Client: Workiva Version 2.1 Caleb Brose, Chris Fogerty, Nick Miller, Rob Sheehy, Zach Taylor November 11, 2014 Contents 1 Problem Statement...

More information

Building the Internet of Things Jim Green - CTO, Data & Analytics Business Group, Cisco Systems

Building the Internet of Things Jim Green - CTO, Data & Analytics Business Group, Cisco Systems Building the Internet of Things Jim Green - CTO, Data & Analytics Business Group, Cisco Systems Brian McCarson Sr. Principal Engineer & Sr. System Architect, Internet of Things Group, Intel Corp Mac Devine

More information

unisys Unisys Stealth(cloud) for Amazon Web Services Deployment Guide Release 1.0 January 2016 8205 5658-001

unisys Unisys Stealth(cloud) for Amazon Web Services Deployment Guide Release 1.0 January 2016 8205 5658-001 unisys Unisys Stealth(cloud) for Amazon Web Services Deployment Guide Release 1.0 January 2016 8205 5658-001 NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information

More information

Linux A first-class citizen in Windows Azure. Bruno Terkaly bterkaly@microsoft.com Principal Software Engineer Mobile/Cloud/Startup/Enterprise

Linux A first-class citizen in Windows Azure. Bruno Terkaly bterkaly@microsoft.com Principal Software Engineer Mobile/Cloud/Startup/Enterprise Linux A first-class citizen in Windows Azure Bruno Terkaly bterkaly@microsoft.com Principal Software Engineer Mobile/Cloud/Startup/Enterprise 1 First, I am software developer (C/C++, ASM, C#, Java, Node.js,

More information

DevOps Best Practices for Mobile Apps. Sanjeev Sharma IBM Software Group

DevOps Best Practices for Mobile Apps. Sanjeev Sharma IBM Software Group DevOps Best Practices for Mobile Apps Sanjeev Sharma IBM Software Group Me 18 year in the software industry 15+ years he has been a solution architect with IBM Areas of work: o DevOps o Enterprise Architecture

More information

1. Please login to the Own Web Now Support Portal (https://support.ownwebnow.com) with your email address and a password.

1. Please login to the Own Web Now Support Portal (https://support.ownwebnow.com) with your email address and a password. Web Hosting Introduction The purpose of this Startup Guide is to familiarize you with Own Web Now's Web Hosting. Own Web Now offers two web hosting platforms, one powered by Linux / PHP and the other powered

More information

LinuxWorld Conference & Expo Server Farms and XML Web Services

LinuxWorld Conference & Expo Server Farms and XML Web Services LinuxWorld Conference & Expo Server Farms and XML Web Services Jorgen Thelin, CapeConnect Chief Architect PJ Murray, Product Manager Cape Clear Software Objectives What aspects must a developer be aware

More information

Orchestrating Document and Media Management using CMIS

Orchestrating Document and Media Management using CMIS Orchestrating Document and Media Management using CMIS Technical Note - Integrating ActiveVOS with Alfresco CMIS Services AN ACTIVE ENDPOINTS TECHNICAL NOTE 2009 Active Endpoints Inc. ActiveVOS is a trademark

More information

A Java proxy for MS SQL Server Reporting Services

A Java proxy for MS SQL Server Reporting Services 1 of 5 1/10/2005 9:37 PM Advertisement: Support JavaWorld, click here! January 2005 HOME FEATURED TUTORIALS COLUMNS NEWS & REVIEWS FORUM JW RESOURCES ABOUT JW A Java proxy for MS SQL Server Reporting Services

More information

Installing an open source version of MateCat

Installing an open source version of MateCat Installing an open source version of MateCat This guide is meant for users who want to install and administer the open source version on their own machines. Overview 1 Hardware requirements 2 Getting started

More information

OpenShift. OpenShift platform features. Benefits Document. openshift. Feature Benefit OpenShift. Enterprise

OpenShift. OpenShift platform features. Benefits Document. openshift. Feature Benefit OpenShift. Enterprise openshift Benefits Document platform features Feature Benefit FOR APPLICATIO DEVELOPMET Self-Service and On-Demand Application Stacks By enabling Developers with the ability to quickly and easily deploy

More information

Web Sites, Virtual Machines, Service Management Portal and Service Management API Beta Installation Guide

Web Sites, Virtual Machines, Service Management Portal and Service Management API Beta Installation Guide Web Sites, Virtual Machines, Service Management Portal and Service Management API Beta Installation Guide Contents Introduction... 2 Environment Topology... 2 Virtual Machines / System Requirements...

More information

FI-WARE Generic Enablers technical overview. University of Athens

FI-WARE Generic Enablers technical overview. University of Athens FI-WARE Generic Enablers technical overview University of Athens 1 FI-WARE: Major Technical Chapters Advanced middleware and interfaces to Network and Devices Advanced Web-based User Interface Applications/Services

More information

Getting Started with Google Cloud Platform

Getting Started with Google Cloud Platform Chapter 2 Getting Started with Google Cloud Platform Welcome to Google Cloud Platform! Cloud Platform is a set of modular cloud-based services that provide building blocks you can use to develop everything

More information

Mitra Innovation Leverages WSO2's Open Source Middleware to Build BIM Exchange Platform

Mitra Innovation Leverages WSO2's Open Source Middleware to Build BIM Exchange Platform Mitra Innovation Leverages WSO2's Open Source Middleware to Build BIM Exchange Platform May 2015 Contents 1. Introduction... 3 2. What is BIM... 3 2.1. History of BIM... 3 2.2. Why Implement BIM... 4 2.3.

More information

CloudCenter Full Lifecycle Management. An application-defined approach to deploying and managing applications in any datacenter or cloud environment

CloudCenter Full Lifecycle Management. An application-defined approach to deploying and managing applications in any datacenter or cloud environment CloudCenter Full Lifecycle Management An application-defined approach to deploying and managing applications in any datacenter or cloud environment CloudCenter Full Lifecycle Management Page 2 Table of

More information

Mobile Cloud Computing T-110.5121 Open Source IaaS

Mobile Cloud Computing T-110.5121 Open Source IaaS Mobile Cloud Computing T-110.5121 Open Source IaaS Tommi Mäkelä, Otaniemi Evolution Mainframe Centralized computation and storage, thin clients Dedicated hardware, software, experienced staff High capital

More information

TIBCO Spotfire Statistics Services Installation and Administration Guide. Software Release 5.0 November 2012

TIBCO Spotfire Statistics Services Installation and Administration Guide. Software Release 5.0 November 2012 TIBCO Spotfire Statistics Services Installation and Administration Guide Software Release 5.0 November 2012 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH

More information

Customer Bank Account Management System Technical Specification Document

Customer Bank Account Management System Technical Specification Document Customer Bank Account Management System Technical Specification Document Technical Specification Document Page 1 of 15 Table of Contents Contents 1 Introduction 3 2 Design Overview 4 3 Topology Diagram.6

More information

OpenShift and Cloud Foundry PaaS: High-level Overview of Features and Architectures

OpenShift and Cloud Foundry PaaS: High-level Overview of Features and Architectures OpenShift and Cloud Foundry PaaS: High-level Overview of Features and Architectures by Alexander Lomov, R&D Engineer at Altoros 2 Table of Contents: 1. Executive Summary... 3 2. The History of OpenShift

More information

Best Practices for Deploying and Managing Linux with Red Hat Network

Best Practices for Deploying and Managing Linux with Red Hat Network Best Practices for Deploying and Managing Linux with Red Hat Network Abstract This technical whitepaper provides a best practices overview for companies deploying and managing their open source environment

More information

Copyright Pivotal Software Inc, 2013-2015 1 of 10

Copyright Pivotal Software Inc, 2013-2015 1 of 10 Table of Contents Table of Contents Getting Started with Pivotal Single Sign-On Adding Users to a Single Sign-On Service Plan Administering Pivotal Single Sign-On Choosing an Application Type 1 2 5 7 10

More information

Portable, Interoperable Cloud Applications using TOSCA

Portable, Interoperable Cloud Applications using TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard Portable, Interoperable Cloud Applications using TOSCA Demonstrated using: Vnomic s Service Designer, IBM ISM Cloud Marketplace

More information

CA Workload Automation (DE) Application and Web Services Agents. John Crespin

CA Workload Automation (DE) Application and Web Services Agents. John Crespin CA Workload Automation (DE) Application and Web Services Agents John Crespin Agenda > Evolution of the Workload Automation > Application Services Agent > Web Services Agent 1 October 16, 2009 CA Workload

More information

NCTA Cloud Operations

NCTA Cloud Operations NCTA Cloud Operations 093018 Lesson 1: Cloud Operations Topic A: Overview of Cloud Computing Solutions Identify the core concepts of cloud computing. Operations Terminology Identify the terminology used

More information

An Oracle White Paper September 2013. Oracle WebLogic Server 12c on Microsoft Windows Azure

An Oracle White Paper September 2013. Oracle WebLogic Server 12c on Microsoft Windows Azure An Oracle White Paper September 2013 Oracle WebLogic Server 12c on Microsoft Windows Azure Table of Contents Introduction... 1 Getting Started: Creating a Single Virtual Machine... 2 Before You Begin...

More information

Alfresco Enterprise on AWS: Reference Architecture

Alfresco Enterprise on AWS: Reference Architecture Alfresco Enterprise on AWS: Reference Architecture October 2013 (Please consult http://aws.amazon.com/whitepapers/ for the latest version of this paper) Page 1 of 13 Abstract Amazon Web Services (AWS)

More information

Java Development for the Cloud, present and future. Scott Rich Distinguished Engineer, IBM Rational srich@ch.ibm.com

Java Development for the Cloud, present and future. Scott Rich Distinguished Engineer, IBM Rational srich@ch.ibm.com Java Development for the Cloud, present and future Scott Rich Distinguished Engineer, IBM Rational srich@ch.ibm.com Java in the Cloud, Today and Tomorrow Changing times Changing tools the rise of PaaS

More information

This presentation provides an overview of the architecture of the IBM Workload Deployer product.

This presentation provides an overview of the architecture of the IBM Workload Deployer product. This presentation provides an overview of the architecture of the IBM Workload Deployer product. Page 1 of 17 This presentation starts with an overview of the appliance components and then provides more

More information

Welcome to the Force.com Developer Day

Welcome to the Force.com Developer Day Welcome to the Force.com Developer Day Sign up for a Developer Edition account at: http://developer.force.com/join Nicola Lalla nlalla@saleforce.com n_lalla nlalla26 Safe Harbor Safe harbor statement under

More information

w w w. u l t i m u m t e c h n o l o g i e s. c o m Infrastructure-as-a-Service on the OpenStack platform

w w w. u l t i m u m t e c h n o l o g i e s. c o m Infrastructure-as-a-Service on the OpenStack platform w w w. u l t i m u m t e c h n o l o g i e s. c o m Infrastructure-as-a-Service on the OpenStack platform http://www.ulticloud.com http://www.openstack.org Introduction to OpenStack 1. What OpenStack is

More information

OpenStack Introduction. November 4, 2015

OpenStack Introduction. November 4, 2015 OpenStack Introduction November 4, 2015 Application Platforms Undergoing A Major Shift What is OpenStack Open Source Cloud Software Launched by NASA and Rackspace in 2010 Massively scalable Managed by

More information

QuickSpecs. HP Helion Development Platform. Overview

QuickSpecs. HP Helion Development Platform. Overview Overview What is it? The is a service that enables developers to rapidly develop, deploy and scale applications across a mix of public and private clouds. We provide support for applications developed

More information

Property & Casualty Insurance Solutions from CCS Technology Solutions

Property & Casualty Insurance Solutions from CCS Technology Solutions Property & Casualty Insurance Solutions from CCS Technology Solution presents OneTimePortal (Powered by WEBSPHERE), Web-based software platform for property and casualty insurers that are seeking to reduce

More information

Instant Chime for IBM Sametime For IBM Websphere and IBM DB2 Installation Guide

Instant Chime for IBM Sametime For IBM Websphere and IBM DB2 Installation Guide Instant Chime for IBM Sametime For IBM Websphere and IBM DB2 Installation Guide Fall 2014 Page 1 Copyright and Disclaimer This document, as well as the software described in it, is furnished under license

More information

Service Oriented Architecture 1 COMPILED BY BJ

Service Oriented Architecture 1 COMPILED BY BJ Service Oriented Architecture 1 COMPILED BY BJ CHAPTER 9 Service Oriented architecture(soa) Defining SOA. Business value of SOA SOA characteristics. Concept of a service, Enterprise Service Bus (ESB) SOA

More information

Oracle Reference Architecture and Oracle Cloud

Oracle Reference Architecture and Oracle Cloud Oracle Reference Architecture and Oracle Cloud Anbu Krishnaswamy Anbarasu Enterprise Architect Social. Mobile. Complete. Global Enterprise Architecture Program Safe Harbor Statement The following is intended

More information

Creating Microsoft Azure Web Sites

Creating Microsoft Azure Web Sites Microsoft Azure supports several ways to create web sites. Of the available Microsoft Azure offerings, Cloud Services and Virtual Machines are the most flexible. While both of these approaches allow a

More information

Automated Data Ingestion. Bernhard Disselhoff Enterprise Sales Engineer

Automated Data Ingestion. Bernhard Disselhoff Enterprise Sales Engineer Automated Data Ingestion Bernhard Disselhoff Enterprise Sales Engineer Agenda Pentaho Overview Templated dynamic ETL workflows Pentaho Data Integration (PDI) Use Cases Pentaho Overview Overview What we

More information

Mobile Data Virtualization. From Managing Devices, to Apps, to Business Data through Mobile Data Access APIs

Mobile Data Virtualization. From Managing Devices, to Apps, to Business Data through Mobile Data Access APIs Mobile Data Virtualization From Managing Devices, to Apps, to Business Data through Mobile Data Access APIs INTRODUCTION Most enterprise mobile applications have one thing in common: they need to access

More information

Benjamin San Souci & Maude Lemaire

Benjamin San Souci & Maude Lemaire Benjamin San Souci & Maude Lemaire introduction What is Node.js anyway? a complete software platform for scalable server-side and networking applications open-source under the MIT license comes bundled

More information

The Great Office 365 Adventure

The Great Office 365 Adventure COURSE OVERVIEW The Great Office 365 Adventure Duration: 5 days It's no secret that Microsoft has been shifting its development strategy away from the SharePoint on-premises environment to focus on the

More information

Google Cloud Platform The basics

Google Cloud Platform The basics Google Cloud Platform The basics Who I am Alfredo Morresi ROLE Developer Relations Program Manager COUNTRY Italy PASSIONS Community, Development, Snowboarding, Tiramisu' Reach me alfredomorresi@google.com

More information

White Paper. Cloud Native Advantage: Multi-Tenant, Shared Container PaaS. http://wso2.com Version 1.1 (June 19, 2012)

White Paper. Cloud Native Advantage: Multi-Tenant, Shared Container PaaS. http://wso2.com Version 1.1 (June 19, 2012) Cloud Native Advantage: Multi-Tenant, Shared Container PaaS Version 1.1 (June 19, 2012) Table of Contents PaaS Container Partitioning Strategies... 03 Container Tenancy... 04 Multi-tenant Shared Container...

More information