How to change the archive storage path of the publish point (IIS media services)?
By default the video stores in inetpub >> media >> archives >> ........
I want to change it to some other location on the network not within the same computer.
Thanks
Dev
There are two ways to change the archive path.
The first method is global for all publishing points :
Run the IIS Manager;
Select the first node on the left panel;
Select Live Smooth Streaming in the features view;
Change the archive path settings.
The second method is for one specific publishing point :
Open the publishing point file (.isml) that you want change the archive path with your favorite text editor;
Add this line between head attribute :
<meta name="archivePath" content="\\path\to\archive" />
The second method is useful when you create a publishing point from a script and not from IIS Media Service.
By default, the archive path property contained in file override the IIS Media Service archive path configuration.
vincex86 is right without one point. I had a problem after changing archivePath. Don't forget to give "Write" permission to IIS_IUSRS user on specified folder
Related
I want to access this archive file :
ftp://Admin_Express_ext:Dahnoh0eigheeFok#ftp3.ign.fr/ADMIN-EXPRESS_3-1__SHP__FRA_WM_2022-02-17.7z
(found on this page : https://geoservices.ign.fr/adminexpress )
Though it seems that the File Transfer Protocol might be used to proceed to the download and I don't figure out how it works on a web browser. How can I access the file then ?
In FileZilla, paste the name of the domain (in this case ftp://ftp3.ign.fr/) in the host box.
After a few seconds you'll be connected to the remote server where the files are located.
The files are located in the bottom right panel, simply drag and drop the file at the place you've chosen on your computer (bottom left panel).
I created a web app on Azure. I am having issues adding additional html pages beyond an index. Is there something I'm missing? I've been searching to no avail.
Looks like you want to define your own start page name for the web app.
Files added to root path(aka wwwroot folder in kudu) can't be accessed with https://webappname.azurewebsites.net unless you set Default document in Application settings. Just add your file name in the list. The first matching file in the list is used.
If your page is deployed to a folder under root path, you also need to set Virtual applications and directories(also in Application settings). Change the physical path value from site\wwwroot to site\wwwroot\foldername.
I follow the training step,
new a SSP application
set application folder (include setting applications publisher)
check the folder in /SSP applications
build a XXX.ssp in there. (used eclipse IDE, and upload it)
show up the XXX.ssp file --> used
http://shopping.na1.netsuite.com/c.TSTDRV0000000//XXX.ssp?n=1
but, still show up "page not found"
what did I miss?
You need to include the path to your ssp folder. It's not the file cabinet folder but the path you set up in the SSP Application definition.
e.g. http://shopping.na1.netsuite.com/c.TSTDRV0000000/path-to-ssp/XXX.ssp
I want to find the correct place to save my user settings for my uwp app. I know there exists:
local: Data that exists on the current device and is backed up in the cloud
roaming: Data that exists on all devices on which the user has installed the app
temporary: Data that could be removed by the system any time the app isn't running
-localcache: Persistent data that
exists only on the current device
I can access the above places with ApplicationData.Current. Which are located somewhere in C:\Users\bla\AppData\Local\Packages\1e7e-94a6-4235-a0c5-9b143f8b_8webbwe
The project also contains a Asset folder, and I can't find a good source which tells me where the folder is located when the app is installed (not in developer mode).
Some developers place there settings into the asset folder. Why? What's the advantage? Is there also a file size limit like for ApplicationData.Current ? When deploying a settings folder into the asset folder will it be available for all user which installed my app? Any background informations regarding the asset folder are appreciated.
Settings files are most appropriate in the ApplicationData folders or ApplicationData.LocalSettings or .RoamingSettings See Store and retrieve settings and other app data
The assets folder is purely a convention. The "assets" name is not special other than to suggest what types of files go in the folder. It is just a useful way to organize the application package to have a place for assets (images, etc.) that are used in the app.
When the app is installed the assets will be in the Package.InstalledLocation directory and can be addressed with an ms-appx:///assets/ URI. Typically this will end up somewhere in \Program Files\WindowsApps\.
Putting a settings file in assets would be a bad idea as the InstalledLocation is read-only and as settings are user data.
There is no hard size limit for files in ApplicationData folders, although if too much data is stored in RoamingFolder then it won't roam. The files will still be available locally.
Need to publish the JS and CSS files using multimedia components.
The multimedia components gets published outside the website folder similar to the Images in
“C:\tridion\temp\pub14\Includes\scripts”
Any Idea How to Configure the multimedia components to get published inside the website folder.
We are using IIS to deploy website
You can control this by editing cd_storage_conf.xml. In this file you can configure where binaries go for each publication. For example: you probably have something like this configured: <Item typeMapping="Binary" cached="false" storageId="myStorageId"/> and this myStorageId storage is defined inside the Storages element like:
<Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory"
Id="myStorageId" defaultFilesystem="true" defaultStorage="true">
<Root Path="c:\temp\" />
</Storage>
If that is the case then you need to change the root path to point to the root of your WebApplication in IIS. More about how to configure the storage you have here (logon required).
You can overide the path of your multimedia binary using template code as long as you have structure group created for same path.
Ex if you want to publish particular binary to \css\images folder, you first have to create the structure group for same path(\css\images) and use the structure group id in the following code to publish the binary.
engine.AddBinary(Binary.Id, templateID, binaryStructureGroupID, Binary.BinaryContent.GetByteArray(), Binary.FileName);