Codekko Software| Product FAQs

How do I contact technical support for assistance?
* To contact Codekko Support, please dial 1-877-461-8767 and select number 2 from the menu. Or email support@codekko.com.

I already use an application delivery controller for application optimization. Why do I need Codekko?
* An ADC is a network solution used to speed the delivery of applications from the local area network across the wide area network to improve bandwidth utilization, productivity, and user experience for enterprise applications and web applications. The segment speaks to WAN optimization as well as acceleration. Methods include compression, caching, traffic prioritization, bandwidth optimization, traffic monitoring, data reduction, and protocol acceleration.
* Codekko’s technology optimizes the web application at the web server, reducing the need for the use of downstream compression and bandwidth optimization as the footprint of the application is reduced at the source. However, Codekko can also compliment the use of the ADC and increase the performance of both ADCs and CDNs.

I am using compression and caching tools on my web server. Do I need to get rid of these technologies?
* Codekko can replace the current compression and caching tools that you may be using or we can be additive to their performance. Below is a comparison of Codekko to other technologies used for application acceleration.

I know that Codekko technology optimizes the web application, but content is the biggest bottleneck on my site. Does Codekko improve the content performance?
* Codekko optimizes the web application and streamlines the javascript used to build the pages at the client. Codekko provides a range of compression capabilities from no compression to maximum compression which along with the optimization of the application framework increases performance and reduces page response times.

I am deploying my applications in the cloud. How does Codekko support this?
* Codekko can be deployed into cloud architectures whether IaaS or PaaS to reduce footprint and increase performance. In IaaS architecture, Codekko is deployed in a virtual environment just as it would be on-premise. Codekko has also been tested within the Microsoft Azure environment for support of PaaS.

What are the server requirements to run Codekko?
* The Codekko software operates on Microsoft Windows Server platforms using Internet Information Services (IIS) Release 6.0 or later for ASP.NET processing. Version 2.0 or later of the .NET framework is also required to run this software.

For 32-bit Operating Systems:
• Windows 2003 Server Standard, Enterprise, and Datacenter
• Windows 2003 Server Web Edition, Small Business Edition

For 64-bit Operating Systems:
• Windows 2003 Server Standard, Enterprise, and Datacenter
• Windows 2003 Server Web Edition, Small Business Edition
• Windows 2008 Server Standard, Enterprise, and Datacenter
• Windows 2008 Web Edition and Small Business Edition

Does the Codekko solution touch my source code?
* No, we do not touch the customer’s source code. We take what the developers created and improve upon it by working with compiled executable files. The interaction with the code is similar to that of a compiler.

Will Codekko break my web application?
* Codekko will not break your web application. When Codekko optimizes the application, the original application is left intact. Also, Codekko optimizes the “compiled” version of the application and does not touch the original source code. The Codekko ISAPI filter acts as a traffic cop and will determine if the optimized or original version of a page should be served to a request. If there is an error, the filter will automatically revert to the original application page and this will be logged for review by an administrator.

What does the installation process look like?
* Installation is easy and can be accomplished in as little as 30 minutes. It constitutes a single software download targeted to the applicable server environment.
* Requirements include: a) accurate identification of applicable servers; b) login and admin access rights into the OS/servers and applications.

What are the best application environments to target for either a pilot or production?
* Web applications developed in ASP or .Net (see above for supported versions).
* Highly user interactive; lots of screens; lots of activity between the application and the user.
* Complex web based applications – account management, order management, ecommerce, inventory management, web based insurance claims, enrollment, corporate portals, travel solutions, etc.

How can I roll back the solution if needed post-implementation?
* Remove all of the optimized code and restore the original code by running the “clean” command.

How does the optimization impact our ability to debug the application?
* Optimization of the application would take place once the developed application has been thoroughly tested in your SDLC and is production ready.
* As the original application is not touched, the software will fail back to the original page if there is any problem found in the optimized page.

Will I need to modify my software development lifecycle? E.g., development, testing, deployment.
* The optimized application will require minimal changes to the load testing procedures. Functional testing should not be impacted by optimization as this would occur prior to the application being optimized. Codekko provides best practice documentation on load testing.

Are there deployment limitations?
* Yes, there are a limited number of scenarios which may require an administrator to exclude pages from being optimized or may require some special setup. These are documented in the administrator’s manual.

How can I support my regulatory audit requirements?
* Liken the Codekko solution application interaction to implementing compression. Log files will have a record of what was optimized on which server and at what time. The log files should not be viewed as material to compliance.