Introduction
This article will be about basic installation of a product from IBM which is ELM (Engineering Lifecycle Management).
The ELM product underwent a significant update and changed from CLM (Collaborative Lifecycle Management) to ELM, while the applications of the ELM package also underwent major updates. The current version we are installing is 7.0.2 SR1 (ifix15), while in the future it is planned to switch to the installation of version 7.0.3.
This product is primarily intended for customers from healthcare, military, transportation and many other critical areas of industry. Among the main common requirements of these areas of the industry are speed, reliability, flexibility, security, etc. In addition to installation itself, important aspects of system deployment include consideration of memory requirements and backup, monitoring, and security processes.
Purpose of the article – challenges
After defining the client's requirements (required applications), the necessary licenses are chosen and the commercial side of the installation is agreed upon. Later, the technical design of the requirements necessary for the deployment of the system is realized, which consists of determining the layout of the applications and the allocation of the required memory resources on the servers.
IBM ELM offers several applications, some of which are listed below:
- JTS (Jazz Team Server)
- CCM (Change and Configuration Management)
- RM (Requirements Management)
- QM (Quality Management)
- ENI/RELM (IBM Engineering Lifecycle Optimization - Engineering Insights)
- AM (IBM Engineering Systems Design Rhapsody – Model Management)
- GC (Global Configuration Management)
- LDX (Link Index Provider)
- Jazz Reporting Service, where are more applications:
- RS (Report Builder)
- DCC (Data Collection Component)
- LQE (Lifecycle Query Engine)
- JAS (Jazz Authorization Server)
- RPENG (Document Builder) – which is implement as separate application/system
To maximize the performance of each application, the most suitable solution is to deploy it on a separate server, which significantly increases the financial requirements, and therefore this approach is mainly suitable for large companies. For medium-sized and small-sized companies (customers), due to their possible financial limitations, the deployment of the IBM ELM solution can be optimized so that multiple applications are deployed on one server at the same time. An example is the following combination of application distribution in the case of using five application servers (ASx):
- AS1: JTS, LDX, GC
- AS2: QM, CCM
- AS3: DCC, RPENG
- AS4: LQE, RS, RELM
- AS5: RM
-
For a better understanding of the architecture, the following figure shows a proposal for a possible logical topology:
1.) IBM ELM Installation Topology
Preferred solutions
The recommendation for large customers is to install each application on a separate server, if the technical limitations of the customer's environment allow it. This results in an increased need for server care, which consists of installation, upgrade, backup and security.
For small and medium-sized customers, we recommend bundling/installing less-used applications together. However, over time, problems with memory and system resource utilization may occur. Detection and prevention of these problems is possible by deploying a suitable monitoring system.
Since customers mostly use the DNG (Doors Next Generation) application from the RM system, it is best to install this application on a separate server. It is also advisable to install applications that the customer uses regularly and contain thousands to millions of "artefacts" on separate servers. Other, less computing and memory intensive applications can be installed together.
An essential part of every ELM deployment is the JTS application, which ensures the connection of individual applications. Another very important part of the infrastructure is the IHS (IBM HTTP Server), which by default works in conjunction with the Reverse Proxy. These components form the "interface" between the internal topology and the external Internet.
Another important element is the use of a database server. Most of the data for IBM ELM applications is stored on this server. The basic databases included in the installation include Apache Derby, which is intended primarily for testing purposes with a maximum of 10 users. This database, according to the documentation, is not intended for a production environment, and therefore we do not recommend it for a production environment. Databases suitable for both production and testing include:
- IBM DB2
- Oracle
- Microsoft SQL Server
The use of these databases directly depends on the number of users.
After deploying the database systems, it is necessary to deploy security in the form of authentication systems. For production, the LDAP (Lightweight Directory Access Protocol) protocol is most often used, while in case of limitations, it is possible to use the IBM product WebSphere Liberty basic registry, which is part of the basic installation, for testing purposes.
Before installation, it is also necessary to take into account the choice of operating system, where Linux and Microsoft Windows are among the most used.
Specialized solutions, approached and tips
By default, installations are performed remotely using remote management tools, depending on the customer.
From Softacus point of view, we try to adapt to customers and carry out installations according to their usual standards. Before the actual installation, it is necessary to ensure access to the customer from an external (the environment of the technician performing the installation) environment.
Due to the need for a secure communication link, VPN (Virtual Private Network) technologies are used, which later complement the IHS and Reverse proxy systems. Before starting the installation, it is still necessary to check whether there is enough free space on the servers.
During installations, it is necessary to guarantee that installed IBM ELM applications do not have access to devices and environments for which they do not have authorization. Attention should also be paid to the installation of applications that are listed as "package" (an application with a set of sub-applications to choose from - the client chooses which sub-applications he needs). After installation and subsequent setting of the environment, it is necessary to verify the functionality of the system, which is assisted by the testing team (Softacus).
As mentioned earlier in the article, the last part of the installation is the backup and planning of disaster recovery procedures, which enables the protection of data against loss and possible damage. The infrastructure being created also includes monitoring systems, thanks to which it is possible to detect and later react in advance to undesirable events on servers and applications.
Conclusion
As you can see, installation is not just about installing one application. It is a continuous and complicated process during which it is possible to implement new functionalities and extensions into the customers' environment.
Softacus Services
We, in Softacus, are experts when it comes to consulting and service delivery of IBM software products and solutions in your business. We help our clients to improve visibility and transparency when licensing and managing commercial software, providing measurable value while increasing efficiency and accountability and we are providing services in different areas (see Softacus Services).
IBM ELM extensions developed by Softacus are free of charge for the customers who ordered IBM ELM licenses via Softacus or for the customers who ordered any of our services. If you are interested in any of our IBM ELM extensions, you found a bug or you have any enhancement request, please let us know at info@softacus.com.
Related and Referenced Topics
Blog Articles:
Basics of Links and Link Types in IBM DOORS Next Generation - learn the basics about the linking and link types in IBM DOORS Next.
Linking Techniques in IBM DOORS Next - article explaining basic concepts and showing multiple ways of creation of links between artifacts.
Link By Attribute Feature in IBM DOORS Next - the article explains how to use the "Link by attribute" function to automatically create, update, or delete one or more links between artifacts based on values in the attributes of the artifact.
Softacus Widgets:
Link Switcher - widget developed by Softacus, that converts the context of artifacts links in a very short time.
Module Link Statistics - extension that provides users with a quick overview of the amount of the links in specific link types in a module.
Link Type Change- extension developed by Softacus designed to enhance the functionality of DOORS Next Generation by allowing users to manipulate the direction of a link or convert it to another type of link.
Links Builder- extension that allows the users to create a link between two artifacts in DOORS Next Generation according to the certain rules.
Link by Foreign Attribute - this extension allows users to create links between artifacts in the selected module(s), based on the attributes values.
Show Attributes of Linked Artifacts - this extension shows the attributes and links of the artifact that is currently selected.
