# Is the value of ${com.wowza.wms.ConfigHome} exposed via the API?

**URL:** <https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613>\
**Category:** Wowza Developer Dojo\
**Tags:** server-administration\
**Created:** [February 8, 2020, 12:07am UTC](https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613 "2020-02-08T00:07:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Moles](https://avatars.discourse-cdn.com/v4/letter/d/f0a364/32.png) [@David\_Moles](https://community.wowza.com/u/David_Moles)\
**Post date:** [February 8, 2020, 12:07am UTC](https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613/1 "2020-02-08T00:07:45Z")

</div>

The REST API exposes some values in terms of path variables, e.g. the default applications have storageDir values like ${com.wowza.wms.context.VHostConfigHome}/content. I can guess that this variable corresponds to the vhost configurationDir, but for the default vhost the value of that is just ${com.wowza.wms.ConfigHome}. I thought I might find this on the server or server/adv object, but it’s not there, and there doesn’t seem to be anyplace above the “server” level to put it.

Is the value of ${com.wowza.wms.ConfigHome} exposed anywhere, or do you just need to know the server installation path?

---

<div class="post-metadata">

**Author:** ![Jason\_Tuchler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_tuchler/32/462_2.png) [@Jason\_Tuchler](https://community.wowza.com/u/Jason_Tuchler)\
**Post date:** [February 10, 2020, 11:33pm UTC](https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613/2 "2020-02-10T23:33:05Z")

</div>

Hello @David Moles

Can you please send a Wowza Streaming Engine REST API call example on how you’re trying to use the ${com.wowza.wms.ConfigHome} variable, and I’ll further look into if this variable is accessible by the REST API.

-JasonT

---

<div class="post-metadata">

**Author:** ![David\_Moles](https://avatars.discourse-cdn.com/v4/letter/d/f0a364/32.png) [@David\_Moles](https://community.wowza.com/u/David_Moles)\
**Post date:** [February 11, 2020, 3:22pm UTC](https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613/3 "2020-02-11T15:22:00Z")

</div>

Sure. My current task is to sort out where the AV files being served by our Wowza Streaming Engine instance actually live, i.e. how the storage directories for each application map to our various NFS servers. To do this, I need the filesystem path on the server for each application.

The first REST query I’m making is to

```auto
http://{host}:8087/v2/servers/_defaultServer_/vhosts/_defaultVHost_/applications

```

which gets me the list of applications. I then loop through this and for each application I make a request to

```auto
/v2/servers/_defaultServer_/vhosts/_defaultVHost_/applications/{application}

```

which gets me the information for that specific application. Part of that result is a **streamConfig** block, e.g.:

```auto
"streamConfig": {
  "serverName": "_defaultServer_",
  "streamType": "default",
  "storageDir": "${com.wowza.wms.context.VHostConfigHome}/content/ucb_only",
  "createStorageDir": false,
  "storageDirExists": true,
  "keyDir": "${com.wowza.wms.context.VHostConfigHome}/keys",
  "httpRandomizeMediaName": false
}

```

The field **storageDir** has the value I’m looking for, but as you can see it’s expressed in terms of **VHostConfigHome**.

If I get the VHost information with a request to

```auto
/v2/servers/_defaultServer_/vhosts/_defaultVHost_

```

I can see the following:

```auto
"configurationDir": "${com.wowza.wms.ConfigHome}"

```

I assume the VHost **configurationDir** property is the same as **VHostConfigHome** , but that’s only an inference on my part. Assuming it’s correct, however, the value of this property is expressed in terms of **ConfigHome** , so it doesn’t actually get me closer to the filesystem path on the server.

Now, as it happens, I know that the server configuration directory is

```auto
/usr/local/WowzaStreamingEngine/conf

```

which is enough to let me get the task done. But going forward, it would be much easier to build reliable tooling around this if I didn’t have to assume this knowledge from outside the system.

---

<div class="post-metadata">

**Author:** ![Library\_IT](https://avatars.discourse-cdn.com/v4/letter/l/fbc32d/32.png) [@Library\_IT](https://community.wowza.com/u/Library_IT)\
**Post date:** [September 14, 2020, 5:15pm UTC](https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613/4 "2020-09-14T17:15:09Z")

</div>

@Jason_Tuchler did you ever have a chance to look into this?

---

<div class="post-metadata">

**Author:** ![video\_streaming](https://avatars.discourse-cdn.com/v4/letter/v/22d042/32.png) [@video\_streaming](https://community.wowza.com/u/video_streaming)\
**Post date:** [September 14, 2020, 8:13pm UTC](https://community.wowza.com/t/is-the-value-of-com-wowza-wms-confighome-exposed-via-the-api/54613/5 "2020-09-14T20:13:15Z")

</div>

He’s out of the office today, but he’ll update you when he returns.