Stay or Modernise? – Considerations for Modernising Legacy Applications
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
Read: [More]
If you are in the process of rolling out systems into new channels (e.g. a mobile presence), migrating toward a cloud-based deployment or integrating with a new partner, you should give consideration to how your systems are integrated. An effective integration infrastructure facilitates business agility, simplifies on premise and in-cloud integration and reduces operating costs.
Traditionally, when organisations developed web-based systems (internal and customer facing) the major elements of the system (application, database, etc) tended to be tightly coupled and integrated. This has led to downstream challenges when organisations have been tasked with delivering new channels such as a mobile presence. In these cases, they have faced the challenge of how to integrate the application for the new channel with the legacy applications. In many cases they choose to tightly integrate the applications. In choosing this integration approach, organisations miss an opportunity to lay a foundation for future business\IT agility and reduced operating cost.
An alternative approach\solution to the above challenge would be to implement a Service Oriented Architecture (SOA) architecture within the environment. In a SOA-based environment, existing applications are made available as discreet, system-independent services. These services may be called by other service enabled applications, inside or outside your organisation (e.g. integrate your Oracle ERP system with a partners/customers SAP system ).
Having a SOA-based infrastructure and service-enabled systems in place enables the organisation to react positively to a number of common business scenarios:
The above scenarios detail how the implementation of a service oriented architecture provides a platform which enables the organisation to react to ever more common business scenarios in an agile, controlled and cost effective manner. It should be noted that the rollout of SOA is not necessarily an all or nothing rollout – The rollout can (and from a risk mitigation perspective should) be undertaken on a project-by-project, incremental basis where the return on investment increases as the number of service-provisioned applications increases).
If you would like further details on any of the topics discussed above, please email John Rushe or call on +353 91 745567.
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
In today's market, finding the correct person to fill contract Oracle positions is a major challenge for businesses. Finding a candidate with the required professional and technical skills to undertake a fixed-term, highly specialized and technical job is almost impossible.
If you are in the process of rolling out systems into new channels (e.g. a mobile presence), migrating toward a cloud-based deployment or integrating with a new partner, you should give consideration to how your systems are integrated. An effective integration infrastructure facilitates business agility, simplifies on premise and in-cloud integration and reduces operating costs.
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
Streamlining the process of migrating from OWB to ODI.
Background: Many Oracle customers currently use the Oracle Warehouse Builder (OWB) product as part of their data warehouse environment. Oracle noted in an OWB Statement of Direction that the current release of OWB (11.2) is the terminal release of the product and that no future releases are envisages. Furthermore, future database releases beyond Oracle Database 12c Release 1 will not be certified with OWB 11.2. On this basis, OWB customers need to identify a strategy and approach to migrate from OWB.
Background: In my previous blog entry: http://www.metalogic.ie/news/9/46/Best-Practice-Code-Organisation-and-Management-for-Oracle-ADF-Applications/d,ML_V2_News_Detail I described some initial considerations when starting a new Oracle ADF project, particularly in relation to ADF modules structure. Another consideration, when starting new ADF projects is that of building the project. In this blog I would like to explain one possible way to approach the application build process.
Using the Oracle Advanced Analytics Database Option can introduce analytic capability into existing Oracle solutions, delivering significant benefits with minimal time, cost and effort.
Recent trends in business intelligence and analytics has seen a shift in interest
Most Oracle ADF project codebases require reorganisation during their lifetime. Getting the structure correct at project outset can save significant effort and pain in the longer term.
A questions that often arises in enterprise software development environments is one of "how do we track requirements, change requests and software bugs. Additionally, how do we track source code to requirements, change requests and software bugs and track issues to software releases? Finally, how do we track time and effort against issues".
There are a number of questions that commonly arise in relation to Oracle database licensing.