Finding an SLM Component UI Path

Introduction
Goals
Building and Deploying a Service Control
Building and Deploying a Service Pack
Finding the SLM Component UI Path
Conclusion

Introduction

The msx-dev-proxy works by layering an alternate UI on top of what is served from an MSX instance using a proxy. This means that until we can use it we first need to build, and package, and deploy the SLM component into MSX. In this guide will show how to use the Chrome Developer Tools to find the path your UI is being server from. We need that information to configure msx-dev-proxy.

Goals

building an SLM component
deploying an SLM component
finding the UI path

Building and Deploying a Service Control

We are going to build a service control project from the examples. Start by downloading the source here, then follow the instructions in the README.

Once you have built and deployed the workflow service control you can find the tile to launch it in Tenant Workspace -> Service Controls. The tile is highlighted in the screenshot below. Note that if your MSX instance does not have any tenants you will need to create one first.

Building and Deploying a Service Pack

The main difference between a Service Control and Service Pack is that you need to subscribe to the latter. There is a separate guide that walks you through generating, building, and deploying a Service Pack (help me).

Finding the SLM Component UI Path

Before you open the service control open the Developer Tools in your browser and select the Network tab. You can also save yourself some headaches by disabling caching. After you have opened the service control look in the Network tab for the path the UI was served from. See the highlighted areas in the screenshot. So in this example the value we are looking for is /workflowexecutorui.

Conclusion

In this guide we built, deployed, and ran an SLM component before using the browser to spy on where the UI was being served from. You can also look in the SLM manifest (help me) for your component to find the context path. We used the Developer Tools as there is often a difference between what should happen and reality. If you jumped straight into this guide the SLM manifest is included in the tarball of the component you upload to MSX (help).

HOME