In today’s rapidly evolving landscape, software and product development teams grapple with an array of challenges, from ensuring traceability to navigating interoperability issues. These obstacles often impede efficiency and hinder progress, underscoring the critical need for advanced solutions. Recognizing the strategic significance of a robust model-driven software engineering tool, we are thrilled to unveil the latest milestone in IBM offerings: IBM® Engineering Systems Design Rhapsody® version 10.0.

This groundbreaking release represents a quantum leap in empowering organizations to navigate the complexities of modern system design, analysis, and validation. With a rich array of new features and enhancements, including a modernized user experience (UX) and expanded profiles such as Harmony MBE, RAAML, and UAF, coupled with seamless integration with the Siemens Capital toolchain, Rhapsody 10.0 heralds a new era of efficiency and innovation.

At its core, Rhapsody 10.0 serves as a comprehensive model-based systems engineering tool, equipping teams with the capabilities to tackle even the most intricate system architectures with ease. By facilitating early validation of requirements, architecture, and behavior, Rhapsody 10.0 significantly reduces the need for rework, thereby optimizing performance and accelerating time-to-market.

One of the defining features of Rhapsody 10.0 lies in its ability to seamlessly integrate systems engineering models and requirements, enabling engineers to develop optimized electronics, electrical, and software architectures. This holistic approach not only aligns designs with sustainability principles but also fosters a culture of innovation through a digital thread framework.

Reindexing is essential for Lifecycle Query Engine (LQE) TRS feeds in cases where the index is disrupted or there is a failure in updating the data source. Exploring options to expedite this procedure is crucial. The duration of this process can vary significantly based on the volume of data involved. Implementing optimized settings and leveraging suitable hardware can effectively minimize reporting delays.

When facing delays in the reindexing process, consider obtaining a javacore as it contains valuable information, such as the number of vCPUs in your environment. This information is crucial for configuring settings to speed up reindexing without overburdening the system. If you need to raise a support case, it’s likely that support will request this information.

Learn how to collect Java cores, thread dumps, heap dumps, and system cores for ELM applications running on the Liberty profile to ensure a comprehensive approach to troubleshooting and performance enhancement.

https://www.ibm.com/support/pages/how-collect-javacores-thread-dumps-heap-dumps-and-system-cores-elm-applications-running-liberty-profile

Steps to take to improve Lifecycle Query Engine (LQE) performance

1.      Reindex individual TRS data sources sequentially, addressing each one that requires reindexing separately. Avoid reindexing all of them simultaneously.

2.      Once the reindexing of the initial TRS data source is complete, select “Pause Indexing.” This step is essential to halt the delta index operations, which typically occur every 60 seconds, thereby conserving server resources.

3.      Evaluate the adjustment of the “Number of threads to fetch artifacts when adding or reindexing this data source” parameter while reindexing. The default setting is 2, but it can be augmented based on the number of virtual CPUs (vCPU). If your system boasts over 20 vCPUs and the data provider server can handle the additional load, consider elevating the thread count to 6-8. In the case of most multi-core CPUs, a temporary increase to 4 is generally deemed safe. Notably, on Intel systems, exceeding 4 threads tends to yield minimal enhancements in data retrieval speed.