[SalesForce] Local Web Storage for Apex

Using a contentType of "application/x-unknown" and specifying the desired filename via setting the Content-Disposition header in the controller was key to making this work.

The working solution was the following code:

Controller

public with sharing class SAPGUILauncher {

    public SAPGUILauncher() {
        Apexpages.currentPage().getHeaders().put('Content-Disposition', 'attachment; filename="SAPGUILauncher.sap"');
    }
}

VF

<apex:page controller="SAPGUILauncher" cache="true" contentType="application/x-unknown">[System]
Name={!$Setup.SAPLauncherSettings__c.SAPName__c}
Description={!$Setup.SAPLauncherSettings__c.SAPDescription__c}
Client={!$Setup.SAPLauncherSettings__c.SAPClient__c}
[User]
Language={!$Setup.SAPLauncherSettings__c.SAPLanguage__c}
[Function]
Title={!$Setup.SAPLauncherSettings__c.SAPTitle__c}
Command=ZSFDCVA01_2 P_AUART={!$CurrentPage.Parameters.OrderType}; P_VKORG={!$CurrentPage.Parameters.SalesOrg}; P_VTWEG={!$CurrentPage.Parameters.DistributionChannel}; P_KUNNR={!$CurrentPage.Parameters.SoldToParty}; P_KUNWE={!$CurrentPage.Parameters.ShipToParty}; P_BSTKD={!$CurrentPage.Parameters.PONumber}; P_MATNR={!$CurrentPage.Parameters.MaterialNumber}; P_KWMENG={!$CurrentPage.Parameters.Quantity};
[Options]
Reuse={!$Setup.SAPLauncherSettings__c.SAPReuse__c}
</apex:page>

The error message which you are receiving means that at the point when this code is executed, there is no element rendered in the browser that can be found with the id of menuLink. When you manually execute the statement in the browser console, you're doing so after the entire page has been rendered and menuLink is now in the page context. You will probably find that this script is executing before the DOM is fully loaded even though you've got it at the end of the VF markup. (What tags did you use to do this? <apex:includeScript?)

If you're using <apex: id="yourName" tags for these elements now or in the future, the following may be useful.

Salesforce documentation about accessing the Id as it was rendered in the DOM.

Best Practices for Accessing Component IDs

You don't mention where this ui.js file is stored but depending on the answer to that question, this answer may need to be adjusted to pass references rather than using merge field syntax (which only works within the VF page itself).

If you need to get the generated unique id for the node on the page, you should use the {!$Component.yourTagID} merge field syntax to do so. This mechanism will give you the full id attribute of the element in the page as it was rendered in the browser.

If the path to the component cannot be found as you wrote it, your path is likely incorrect or ambiguous in the page context. It will not throw an error when this happens, it will just return an empty string. i.e. var myVar = ''; where you expected var myVar = 'j_id0:j_id2:myThing'; You can verify what's happening by looking at the source in the browser.

For instance:

(function (window, document) {
    var layout   = document.getElementById('{!$Component.layout}');
    var menu     = document.getElementById('{!$Component.menu}');
    var menuLink = document.getElementById('{!$Component.menuLink}');

or something more targeted to a specific path from the <apex:page id="myPage"> to the element itself:

(function (window, document) {
    var layout   = document.getElementById('{!$Component.myPage.myForm.myPageBlock.layout}');
    var menu     = document.getElementById('{!$Component.myPage.myForm.myPageBlock.menu}');
    var menuLink = document.getElementById('{!$Component.myPage.myForm.myPageBlock.menuLink}');

or if you want to pass the DOM id as a function param:

(function (window, document, layoutId, menuId, menuLinkId) {
    var layout   = document.getElementById(layoutId);
    var menu     = document.getElementById(menuId);
    var menuLink = document.getElementById(menuLinkId);

    // check for nulls

    // content trimmed for brevity

}(this, this.document, '{!$Component.layout}', '{!$Component.menu}', '{!$Component.menuLink}'));