Demonstration of using Subversion for OScript development. The basic script of this demo is as follows: (1) A new module is imported into Subversion and tagged as verison 1.0.0. (2) The module is checked out into the staging directory and versioned from 1.0.0 to 1.0.1. (3) The updated module is checked into Subversion and deleted from the staging directory. (4) The module is then exported back into the staging directory and installed. (5) Version 1.0.1 is then checked out and changes are made. (6) The changes are committed back to Subverison and tagged as version 1.0.1. (7) A diff is performed comparing version 1.0.0 and 1.0.1.
In this video, I demonstrate that using an Add Version callback to restrict users from uploading executable files does restrict Discussion posts. Attempting to post either a topic or reply with an executable attachment is prevented by implementing the callback.
This Livelink example shows what a user encounters when they attempt to upload a dll or exe file into a Livelink environment when an Add Version callback has been implemented to prevent this. Because the restriction is implemented as an add version callback, upload of dll or exe files are not only prevented from the web UI. Any operation that requires a version to be added will be restricted. The video explicitly shows the results of trying to do this using the web UI, LAPI or Explorer Pro.
Basic script of video: (1) A text document is added to the environment. (2) The text file is added as a new version to the document. (3) An attempt is made to add notepad.exe as a version. (4) An attempt is made to add a dll as a version. (5) A LAPI program is executed to demonstrate the restriction is enforced for non-web operations. (6) Explorer is used to demonstrate that the restriction is enforced for Explorer clients as well.
The Livelink/Content Server serivce starts the JavaVM automatically. When debugging issues or writing modules, you will observe that all JavaObject related commands fail. This is because Builder does not, by default, start the JavaVM. This is easily remedied by adding the '-loadjavavm' switch to the 'target' property of the shortcut for Builder. This video shows you how to do that.