Portfolio Desktop is the surface layer where IceBreak, IceCap, Architect, and Assist converge - enabling users to interact with data, logic, and workflows without context switching or modular fragmentation.

Architectural Role of the Portfolio Desktop

The Portfolio Desktop is not a superficial web UI - it is a browser-based client orchestrated as part of the native Sitemule runtime environment. Built on top of IceBreak, it delivers real-time, session-aware access to all functional modules. Each application - whether launched from IceCap, generated by Architect, or embedded through Assist - is contained within a tabbed session that maintains execution state, authorization, and transaction context without initiating multiple sessions or duplicating resources.

The layout engine within the Portfolio manages workspaces using a structured, hierarchical configuration. Navigation trees, menu policies, and shortcut bindings are enforced at runtime, with user-specific profiles determining access levels and layout restrictions. Because execution is handled within the same job scope via IceBreak, the transition between screens, actions, or data operations is instant and consistent.

Runtime Behavior and Multi-Module Integration

The Portfolio Desktop coordinates real-time module execution across all four core engines:

• IceCap applications are rendered into tabs and maintain synchronized green-screen-to-web logic.
• Architect applications bind live Db2 structures into filterable, editable data grids presented within the Portfolio’s tab framework.
• Assist delivers contextual AI guidance, either passively in the background or actively in a dedicated side panel, connected to the user's session and operational context.
• IceBreak acts as the runtime server for all of the above, dispatching requests, managing security contexts, and handling session persistence for each tabbed view.

This multi-engine integration is not emulated or containerized - it is native. All modules execute under the same dispatcher, which ensures that memory, session state, and job management remain aligned, eliminating the typical inconsistencies that occur when web UIs are grafted onto disparate backends.

Technical Operation and Functional Enablement

The Portfolio Desktop supports high-concurrency, multi-session workloads with predictable resource control. Every tab is a managed interface for an underlying runtime service, maintaining isolation where needed (e.g., separate transactions) while allowing shared context (e.g., same user profile, role permissions). Session timeout, language preference, layout persistence, and audit tracking are controlled at the infrastructure level, not client-side.

Workflow integration is a core design goal. Tabs can initiate cross-module transactions - for example, launching a data object from Architect based on a validation result from an IceCap screen, or triggering an Assist search in response to a failed process. These interactions are rule-driven, secured by user role definitions, and enforceable by runtime policies defined in IceBreak.

The desktop also supports cross-environment deployment - different tabs can connect to different runtime servers or partitions while appearing in a unified interface. This supports production vs. test sandboxing, or cross-company ERP separation, with no frontend duplication or reconfiguration.

What You Always End Up With

By implementing the Portfolio Desktop, organizations establish a centralized control layer that is:

• Structurally aligned with the native runtime architecture of Sitemule, ensuring stability and minimal resource overhead.
• Capable of running all module types in parallel, with tab-based multitasking that preserves session state across all interactions.
• Fully integrated with role-based access control, layout policy, session lifecycle management, and audit tracking.
• Consistent in performance, thanks to a unified dispatcher model, job pooling, and controlled memory handling at runtime.

Whether in production environments or development scenarios, Portfolio Desktop provides not only the UI but the execution framework needed to coordinate modernized IBM i workloads.

From A to B with Guided Support

Deploying the Portfolio Desktop does not require rebuilding your business logic or frontends from scratch. System & Method ensures that your transition from legacy green screens or fragmented web tools to a unified execution interface is structured, secure, and aligned with best practices.

Our support begins with technical validation - confirming your runtime environment supports layout configuration, dispatcher alignment, and session isolation policies. From there, we assist in configuring access controls, menu hierarchies, tab layout definitions, and integrated module launch logic.

Training is provided on everything from session debugging and interface profiling to module switching and Assist configuration. Your operational team gains not just an interface, but a runtime-integrated workspace for managing, testing, and executing modern IBM i applications.

Whether you're enabling cross-module workflows, managing users in a shared ERP environment, or integrating AI-driven help alongside legacy programs, Portfolio Desktop is your central point of control. With Sitemule, execution is not fragmented - it is unified, structured, and fully supported.

For deployment guidance or platform consultation, contact Support.