Small businesses that offer tech support will turn out better results than a big tech support company offering global support. Having worked in tech support and worked with providers of various sizes, I have come to the opinion that small departments offer more meaningful support, better customer service and have superior knowledge.
This is it. The final installment. The end. Our tunnel of light leading us to the promise land of perfect integrations with Serendipitous Cerebration as our Virgil guiding us through the Malebolge of Content Management.
Serendipitous Cerebration as a problem solving technique can only be applied in the rare cases when normal logical troubleshooting has failed. As much as we hate to admit it, when all logical problem solving avenues have been exhausted and our troubleshooting prowess to a flummoxed state of tentation, this is when we begin to enter the realm where serendipitous cerebration hides in dark, dank crevasses. In reviewing this project, our hopes are that you can see how the process of Serendipitous Cerebration can develop.
I recently worked on a team tasked with a software integration project that connects invoices from between some Accounting software to ILINX® Content Store. The integration software was used for pulling invoice values from both our AP and AR invoices for modifying the image indices for the stored content in ILINX Content Store.
Today’s topic is short and sweet – Backups! Backups are worth their weight in gold to an administrator. Even though backups have never been put on a scale, we know they weigh a lot! In the world of Enterprise Content Management, backups have to be attacked from many different angles usually. System registry, databases, filesystems and more have to be backed up and then integrated back together on a restore, which can be complicated to say the least.
But there is one ECM system that does not require complicated backup strategies: ILINX Content Store! That’s right – all you do is configure database backups. No registries—file system is completely optional and in the event of a recovery, a fast reinstall of the server software and a database reattach is all that is required. Conveniently all the settings, data, and preferences are saved in the database. Compare that backup strategy to other industry-leading ECM systems and you will see how simple it is.
A common recommendation we have when designing Enterprise Content Management systems is the use of multiple environments. I am referring the use of Development, Test, and/or QA environments to complement a Production environment. There are many advantages to deploying systems with multiple environments, and I would like to discuss the role of multiple environments and the advantages to implementing them for your ECM system.
Depending on the size and complexity of the solution different supporting environments are recommended. For, example with a smaller departmental level solution with little or no custom development, it is common to only recommend one supporting environment used for development and testing. Now let’s take another example where a customer has an enterprise level ECM system with custom development and a requirement for minimal system downtime. The following is a common layout for this type of system:
- Development Environment – Used for custom development and preparation for testing changes to the ECM system. This environment is usually much smaller than the Production Environment and is commonly running on virtual servers/machines.
- Test Environment – Used for end to end testing of changes to the system. Changes are certified in this environment prior to moving to the QA or Production. This environment is usually smaller than Production, but it is imperative that the functionality is consistent to ensure proper testing and certification of the changes.
- Quality Assurance Environment – This environment serves a couple of purposes and it closely mirrors the architecture of the Production Environment. Performance load testing and client acceptance are performed in this environment. In some instances, this environment can also serve as a disaster recovery environment in the event of a Production outage.
- Production Environment – Used for the ECM Production System.
This environment configuration is representative of a common layout for multiple environments, but depending on the organization and solution it can vary. The ECM solution architects play a valuable role in recommending the optimal configuration. At ImageSource, we have extensive knowledge and experience with ECM architecture and take a great deal of pride in designing the correct layout for the customer and the solution.