Sunday Jun 26, 2011
Check out these new hardware and software integrated solutions from Oracle Sun (they are not Exa* machines): http://www.oracle.com/us/products/servers-storage/servers/blades/index.html They offer a number of solutions not offered by VBlock: Oracle DB, Oracle WebLogic, OS and end to end management. Be interesting to see how much adoption these machines get given the long time VBlock has been around and the Exa* focused strategy at Oracle.
Wednesday Jun 15, 2011
By llaszews on Jun 15, 2011
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
Migrating legacy client/server and mainframe technologies to the Oracle cloud.
- Migrating blog entries
- Middleware and Cloud Computing Book
- Oracle Enterprise Manager with AWS Database Instance
- AWS EC2 Overview book
- AWS EC2 Oracle RDB - Storing and managing my data
- AWS CloudFormations, Oracle Assembly Builder, Chef and Puppet
- IBM DB2 AIX RISC to Oracle Linux Sun x86
- Amazon CloudFormations and Oracle Virtual Assembly Builder
- Amazon AMIs and Oracle VM templates
- Migrating RISC to x86 - endianess 'issue'