Wednesday May 16, 2012

RISC to x86 migrations - Or CISC to RISC

Migrating from RISC based systems to x86 (CISC based systems) is another type of cloud migration along with application, database, and mainframe z/OS migrations. However, the steps, best
practices, process, methodology, and tools used are the same. The components of the current RISC based architecture that need to be migrated remain the same:
1. On line application
2. Batch application
3. Integration Infrastructure
4. BI and reporting
5. ETL processing
7. Operating System
Note on OS migration: Although an operating system migration is often assumed (UNIX to Windows/Linux) in a RISC to x86 migrations, this does not necessarily need to be the case as Solaris and HP-UX (announced) run on x86.
It may also be the case you are already running Linux on your RISC system so there is no need to migrate the OS. However, you will probably be upgrading to a
newer release of Linux.
8. Operating System scripts and tools
9. Application, network, database and operating system management and monitoring products and tools
10. Other infrastructure software such as DR, replication servers, gateways, back up and recovery ....
11. Hardware refresh - Of course, you will need to purchase, install, configure and test the x86 based hardware platform. This is a great opportunity to consider hardware infrastructure that is
better suited to the cloud such as blades (Dell, CISCO UCS, Sun/Oracle) or engineered systems (Exadata and Exalogic).
Ultimately the question is how long will it take, what are all the activities involved, and how much will it cost. The answer to these questions is based more on the OS migration that is being done
then the move from RISC to x86. Will the application language or 4GL product run on Linux/Windows? What is the impact of moving the database from one OS to another ? (this should be minimal as all major relational databases run on x86). The biggest impact (for the application migration) could be Unix specific KSH or CSH scripts. You may also be running management, monitoring, or older job scheduling tools that
only run on UNIX/RISC.
As you can see, nothing is different here from what I have blogged about regarding mainframe, client/server, and application cloud migrations.
Intel has a comprehensive RISC migration white paper here:
RISC Migration

Thursday Mar 15, 2012

Running applications in the cloud not designed for the cloud

The question of what to do with applications that were written for the mainframe or client/server based applications that do not fit into a shared service model of the cloud has come up a lot in the last few weeks. This is something that is addressed in chapter 8 of the Migrating to the Cloud book. The bottom line is: The issue you face with moving client/server applications to the cloud via rehosting is “where will the applications run?” Currently, your applications are installed on client PC machines or other thick client devices; the Apple iPhone is in the thick client category as you actually download an application that runs on your iPhone; the application now needs to be hosted on a central server accessible through the Web. A handful of products from Oracle and third parties are available for hosting client/server applications in the cloud. Third-party solutions include Citrix XenApp (formerly Citrix WinFrame Server, Citrix MetaFrame Server, and Citrix Presentation Server) and VMware Server. Oracle solutions include Oracle Virtual Server, Oracle Tuxedo, and Oracle Exalogic. Oracle Tuxedo is the leading open systems transaction processor (TP). It supports both COBOL and C/C++ applications, as well as Ruby and Python. Oracle Tuxedo can run on Oracle Exalogic to provide you both the application runtime environment (Tuxedo) and the cloud hardware infrastructure (Exalogic). Oracle Tuxedo can also be deployed on Oracle Virtual Server for a virtualized cloud environment. We will discuss Oracle Virtual Server and Oracle Exalogic in detail in the “Target Hardware and Software Stack Options” section later in this chapter. [Begin WARNING] A client/server application cannot just be moved to a virtual server and be considered cloud-ready. The application is now accessible by many users, so it must be multiuser and multithreaded. Oracle Tuxedo and Oracle WebLogic Server are both multiuser and multithreaded. A single-user C, C++, or Java application can be made multiuser by running this application in Oracle Tuxedo or Oracle WebLogic Server as these application server containers are multiuser and multithreaded. When using Oracle Virtual Server, it needs to be placed into a grid middle tier environment. This environment could consistent of a cluster of commodity hardware components with a load balancer in front of the configuration for managing load balancing (multithreading) and multiuser connections. This virtual server grid can then run hundreds of images of the same application so that the application can service hundreds or thousands of users. [End WARNING]

Thursday Jan 19, 2012

Oracle cloud migration success starts with design

Article on TechTarget is an excerpt from the Migrating to the Cloud book. This excerpt discussing the approaches that can be taken to cloud migrations.
Migrating to the Cloud book excerpt

Wednesday Nov 23, 2011

Oracle PaaS Cloud partner events

Take a look at this partner event that will discuss concepts and architecture to implement and manage Hybrid (Public/Private) Clouds utilizing Engineered Systems from Oracle.
Oracle Cloud partner workshop

Sunday Nov 13, 2011

Mainframe as the cloud ?

Everyone seems to jumping on the 'new' (not new at all) idea that a mainframe can be used in the cloud. SD Times article in October 2011 states: "While datacenter utilization can be tricky to optimize above 30% even with virtualization and workload tools, mainframes tend to run at over 80% of capacity."

Wednesday Nov 09, 2011

Forth Key attribute of Cloud Computing - Provisioning

Provisioning the system from end to end - OS, hardware, storage, application, network and datavase need to be self service provisioned. Provisioning is dynamic and self-service provisioning of applications involves deploying applications to your cloud infrastructure with a few mouse clicks. So, when moving to the cloud, application provisioning will be made easier since there are not hundreds or thousands of client machines to deploy too. Self-service provisioning of computing infrastructure in a cloud infrastructure is also very desirable as it can cut down the time it takes to deploy new infrastructure for a new application or scale up/down infrastructure for an existing application. Public cloud service providers like Savvis, Terremark, and AT&T all have self-service portals where users can sign up for cloud services and their compute infrastructure is ready within hours for usage. Oracle Enterprise Manager provides many Application Programming Interfaces (APIs) that can be incorporated into the self-service portals of cloud providers to automate the provisioning of compute infrastructure for Oracle products such as Oracle Fusion Middleware and Oracle database.

Monday Nov 07, 2011

SSD used for robust applications

Interesting article as flash is a key component of Oracle Exadata, Exalogic and new Superclusters.
Flash to achieve high performance
However, this article is about using flash for a 'regular' Oracle database.

Monday Oct 31, 2011

Win a copy of Migrating to the Cloud - follow me on twitter

Win a copy of this book. All you need to do is starting following me on Twitter Tom Laszewski
After two weeks, I will pick two twitter follows. These two follows will receive a free copy of this book:
Migrating to the Cloud

Friday Oct 14, 2011

Win a free Cloud Book - Just follow me on Twitter

Win a copy of this book. All you need to do is starting following me on Twitter Tom Laszewski
After two weeks, I will pick two twitter follows. These two follows will receive a free copy of this book:
Information Integration, Data Migration and Consolidation

Wednesday Aug 24, 2011

Mainframe Cloud ?

The mainframe really was Cloud 1.0. Very good article here: http://www.infoworld.com/d/data-center/new-job-mainframes-hosting-private-clouds-329. Oracle Exadata and Exalogic are Cloud 2.0. Similar to to Cloud 1.0 but much improved: based upon open standards network, storage, relational databases, Java EE and processors.

Wednesday Jun 15, 2011

Oracle Exalogic VBlock private cloud

The following high level steps (probably others) that would need to be performed to get a the application server software running on a VBlock platform. Because Oracle Exalogic is a hardware and software solution, these steps are not required: 1. Assess your application requirements. This includes what operating systems, database drivers, application server, SOA software, integration software, and application management software is required. 2. Research available component technologies and vendor products. Review the products and technologies from vendors that span operating systems to application management and monitor to application servers. 3. Identify all software components and evaluate their compatibility, required drivers, and vendor certifications. Ensure that the application’s middleware software will work with the hardware you have selected. 4. Obtain application server, management software, and database driver components from vendor(s) for trial use. This includes negotiating with all the vendors to obtain the software required to perform a Proof of Value (POV) or POC. 5. Assemble the software components, including the application software design. 6. Install the base software components sufficient for performing a network test. 7. Test the physical system, working with vendors to identify areas where they will need to supply changes or fixes. 8. Obtain and deploy patches and fixes from software vendors and deploy them to the test system. 9. Repeat steps 7 and 8 until the test environment is stable. 10. Finalize vendor price negotiations, support contracts, and vendor service-level agreements (SLAs). 11. Fully document the platform state and platform-specific operating/maintenance procedures, vendor support engagement practices, and internal triage protocols. 12. Move the system from testing/development to production. 13. Start over when someone changes the application requirements, when a key vendor product is discontinued or reaches end of life (EOL) prematurely, or when a key component vendor is no longer viable. More can be found on migrating to the cloud and how Oracle Exalogic can make migrating to the cloud easier in this book to be released at Oracle OpenWorld: http://www.barnesandnoble.com/w/migrating-to-the-cloud-tom-laszewski/1030832062?ean=9781597496476&itm=1&usri=tom%2blaszewski
About

Migrating legacy client/server and mainframe technologies to the Oracle cloud.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today