208 eClient 101 Customization and Integration
8.1 Design considerations
Before you begin designing and implementing your customized eClient, there are
several important considerations:
Considerations for incorporating future upgrades of eClient
Considerations for working with different EIP back-end servers
EIP back-end access vs direct access to back-end servers
Maximum length of a URL
Variations in Web browsers
In the following sections, we address each of these in detail.
8.1.1 Considerations for incorporating future upgrades of eClient
One very important factor to consider when customizing the eClient is that IBM
will continue to update and enhance eClient. This may include changes to the
servlets, tag libraries, and most importantly, to the JSPs.
Since there are many JSPs that you can modify or replace with your own, it is
important to give careful consideration to how much you customize the JSPs and
how you will merge your customization with future versions of the eClient JSPs.
Keeping your changes manageable and easy to merge into new versions of the
eClient will make it easier to take advantage of new eClient functionality provided
in future versions of the eClient.
There are several things you can do to make this task easier:
1. Minimize the number of changes you make to the eClient JSPs.
This is a very simple yet important concept. While it can be tempting to begin
making small changes to lots of the JSPs to “tweak” the user interface, it is
important to remember that if you want to take advantage of new eClient
features in future releases, most likely you will need to re-apply and re-test
every customization that you make.
2. Keep as much new code as possible out of the JSPs.
Put as much custom code into new code modules outside of the JSPs as
possible. This can be in brand-new JSPs being the view for newly added
functionality (servlets) or new tag libraries. Using tag libraries reduces
complexity in the JSPs, allows implementation reuse, and simplifies migration
to a new eClient version.
3. Clearly mark your custom code in the JSPs.
You can make it easier to find your customizations by putting comments
before and after each change. This has been done in the examples in the