fiogf49gjkf0d take it in steps.
- make sure first that you are testing from the dev machine where all the parts are located and registered.
- then add some functions to the startup script to display status of the application object to verify your code is loaded or recognised.
- we had issues with dependencies not being installed or transfered to the remotes correctly and it took a while to identify what the issue was.
- I recall we also placed the code in the gac or in the slx applications folder (its been a while)
- last item was the slx distribution process does work but you need to get all the pieces parts incorporated in the package, Then thay all need to be self registering, if a component isn't self registering, manually install it first and verify it's in the gac.
Thats basically it, the process as a whole is pretty straight forward. You might try putting a really simple "Hello World" together first and verify the linkage is working under a few senarios, and validate file locations once pushed to a remote. Then beef up your code and track the change.
As i recall when we did it I needed several dependent components and so we manually installed a few items via the network, then pushed the slx package. It worked, but we needed to start slx or reboot in a few cases before it was consistant. A one time thing, updates seemed to work fine after that. |