This should work. The definst is the default application instance name. You need to specify the application instance name if you want to use the FLVPlayback component.
The server does create folders under /applications/appName/ to manage applicationInstances, but you do not have to create them. Just naming it in rtmp url is all you have to do.
There is only one Application.xml per application.
There are no use for subfolders below /conf/[applicationName]
You create applicationInstances just by using them in rtmp url. So simply connecting to Wowza with a rtmp url with applicationInstance part creates that instance:
rtmp://yourWowzaIP/AppName/someAppInstance
“someAppInstance” is created, it just works.
Application instance folders are created by Wowza here:
You made me wonder if I had missed something, but I can’t find anything to support that. I think if you thought this worked before it was a coincidence, i.e., it was working for another reason. Take a look at the Server Architecture and Server Configuration sections of the User Guide.
When you create:
/applications/customer1
/applications/customer2
And
/conf/customer1/Application.xml
/conf/customer2/Application.xml
That is two applications. Correct. Each Application.xml can have a different StreamType.
But this does nothing:
/conf/customer1/someAppInstance
To create an applicationInstance of the customer1 application, you just connect to it:
rtmp://wowzaIP/customer1/someAppInstance
someAppinstance is an instance of the customer1 application and has all the properties set in:
/conf/customer1/Application.xml
It is in its own space. Streams published to someAppInstance can only be subscribed to by clients that connect to the same server/application/applicationInstance named “someAppInstance”
If you do not explicitly specify an applicationInstance, Wowza runs it as definst
Important to note that you can use more than one StreamType in an application. You do it in the Flash client with actionscripot, like this:
//first do this with netconnection
netconnection.call("setStreamType",null,"live");
//second, create a new NetStream object to use with that StreamType
var nsLive:NetStream = new NetStream(netconnection);
that was completely new for me. In the past i always use wowza like this scheme:
conf/Application/ApplicationInstance
this works for our sorting scheme quit good. Is this a Problem to use wowza like this? This is for a quite better Overwiew i already thought.
There is only one Application.xml per application.
There are no use for subfolders below /conf/[applicationName]
How can i handle more than one Stream types in an Application.xml like ondemand, live and liverecord? Because of that we made also this subfolders for each customer.