Installing the MSX Development Proxy

• Introduction
• Goals
• Installation
  • Homebrew
  • coreutils
  • node
  • msx-dev-proxy
• Conclusion

Introduction

If you have written a Service Pack or Service Control that was deployed into MSX as an SLM component, then you will already have experienced the slow debug cycle. This guide explains how to use the msx-dev-proxy to serve the UI for the component locally against a remote MSX instance.

Goals

• install homebrew
• install coreutils
• install node
• install msx-dev-proxy

Installation

Run the terminal commands below to install the software require to run the msx-dev-proxy on an Intel Mac.

Homebrew

$ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

coreutils

$ brew install coreutils
.
.
.
Commands also provided by macOS and the commands dir, dircolors, vdir have been installed with the prefix "g".
If you need to use these commands with their normal names, you can add a "gnubin" directory to your PATH with:
  PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"

node

$ brew install node@14
.
.
.
If you need to have node@14 first in your PATH, run:
  echo 'export PATH="/usr/local/opt/node@14/bin:$PATH"' >> ~/.profile

For compilers to find node@14 you may need to set:
  export LDFLAGS="-L/usr/local/opt/node@14/lib"
  export CPPFLAGS="-I/usr/local/opt/node@14/include"

msx-dev-proxy

$ npm install --save-dev @cisco-msx/dev-proxy
.
.
.

Conclusion

You now have all the software required to serve an SLM component UI locally against a remote MSX instance.

NEXT

HOME