nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pre-configure proxy in WAB base code?

ChrisMathers

Im useing a proxy on my webserver, which uses the esri web-adapter, and want to know if I can pre configure the proxy settings in the base code of WAB Developer. Its a bit annoying to have to copy and paste in the proxy settings to every map when I export them at a new version.

Find more posts tagged with

Accepted answers

ChrisMathers

Wow thanks to Subu suggesting a JS beautifier I found it pretty quick. I used os.walk python to look in every file for "useProxy" and add any that contained it to a list. Then I just beautified the code in those few files before searching through them. In '\server\rest\apps.js' there is a function called zipApp which does what I expected, edits the app config in the deployment zip. I dont know enough JS to tell if it happens before or after zipping but I plugged 'TEST' into the empty url string, saved, exported and there it is in the config.json in the zipfile. Beautified version below, the url is on line 21.

function zipApp(e, t) {
    var n = getAppPath(e);
    n = path.normalize(n);
    try {
        fs.existsSync("./apps/zips") || fs.mkdirSync("./apps/zips");
        var i = fse.readJsonSync(path.join(getAppPath(e), "config.json")),
            r = i.portalUrl;
        "/" !== r.substr(r.length - 1, r.length) && (r += "/");
        var o = new JSZip;
        utils.visitFolderFiles(n, function(e, t, i) {
            var r, a = e.substr(n.length, e.length);
            if (i) o.folder(a);
            else if ("env.js" === a) r = fs.readFileSync(e, {
                encoding: "utf-8"
            }), r = r.replace("//apiUrl = ", "apiUrl = "), o.file(a, r);
            else if ("config.json" === a) {
                var p = fse.readJsonSync(e);
                p.httpProxy = {
                    useProxy: !0,
                    alwaysUseProxy: !1,
                    url: "",
                    rules: []
                }, p.appId = "", o.file(a, JSON.stringify(p))
            } else r = fs.readFileSync(e), o.file(a, r)
        });
        var a = o.generate({
            type: "nodebuffer",
            compression: "DEFLATE"
        });
        fs.writeFileSync(getZipFilePath(e), a, "binary"), t()
    } catch (p) {
        console.log(p), t(p)
    }
}

All comments

ChrisMathers

Oh I agree, but they should expose this in the main interface as something you can set at the start instead of going into the config, which is minified, after export insert the url.

RobertScheitlin__GISP

All,

I find it very unlikely that the development team will share info about modifying any file associated with the builder portion of WAB (it is minified for a reason).

MichaelMiller2

This is awesome. Seems like the development folks could have shared that info with us.

Thanks Chris and Subu!!

ChrisMathers

function zipApp(e, t) {
    var n = getAppPath(e);
    n = path.normalize(n);
    try {
        fs.existsSync("./apps/zips") || fs.mkdirSync("./apps/zips");
        var i = fse.readJsonSync(path.join(getAppPath(e), "config.json")),
            r = i.portalUrl;
        "/" !== r.substr(r.length - 1, r.length) && (r += "/");
        var o = new JSZip;
        utils.visitFolderFiles(n, function(e, t, i) {
            var r, a = e.substr(n.length, e.length);
            if (i) o.folder(a);
            else if ("env.js" === a) r = fs.readFileSync(e, {
                encoding: "utf-8"
            }), r = r.replace("//apiUrl = ", "apiUrl = "), o.file(a, r);
            else if ("config.json" === a) {
                var p = fse.readJsonSync(e);
                p.httpProxy = {
                    useProxy: !0,
                    alwaysUseProxy: !1,
                    url: "",
                    rules: []
                }, p.appId = "", o.file(a, JSON.stringify(p))
            } else r = fs.readFileSync(e), o.file(a, r)
        });
        var a = o.generate({
            type: "nodebuffer",
            compression: "DEFLATE"
        });
        fs.writeFileSync(getZipFilePath(e), a, "binary"), t()
    } catch (p) {
        console.log(p), t(p)
    }
}

ChrisMathers

Hmm that looks like some of the internal workings of the WAB server. I dont see where I could insert the proxy settings. It looks to me like sitemap\config.json is where it should go but in sitemap\copy-list.txt that json file isnt copied to the new apps as they are created/imported. It has to be in there somewhere and I'm determined to dig it out. If that file isnt copied than the config.json in the app folder is freshly created each time, so there must be a default coded in somewhere.

edit: found a clue in client\builder\main.js - nope nevermind.

TimWitt2

Maybe you can modify the proxy.js in your server folder?

ChrisMathers

That's what I've been doing at the app level. I am going to try putting the settings in the base config.json in WAB so it gets applied to every new/imported app. I know you can do this with the widgets but I've not tried with that particular config. It'll save about 30 minutes of opening every config and entering the settings.

TimWitt2

Chris,

this might help you:

Use proxy—Web AppBuilder for ArcGIS | ArcGIS

Tim

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.