Create, Activate, or Move a Storage Profile
Storage profiles provide a flexible way to manage the physical storage of your document images. A storage profile provides a description and pointer to the physical space where documents are stored, usually a hard drive installed locally or on a network. It can also be a folder on a hard drive.
Multiple Storage Profiles: A single Synergize repository can support multiple storage profiles. All profiles can be active for retrieval; however, only one (1) profile can be active for writing (saving files) at a time.
Multiple Synergize Servers or Other Servers: If you have multiple Synergize servers or you have set your storage location to a different machine, the location must be a network share. Furthermore, the security settings on the storage profile directory must be set to read/write for the various computers that may be trying to access the location. This includes all Synergize servers plus, for example, an image micro-service running on Synergize Enterprise Server (SES).
Tip: Local and network (UNC) storage profiles are supported. We do not recommend using mapped drives such as G:\shared for Synergize storage profiles. A mapped drive is user-specific. Instead, use a Universal Naming Convention (UNC) descriptor for your network drives.
Example: \\distantcomputer\shareddrive\
In most configurations, customers prefer to avoid continually adding drives to their existing configuration. Synergize supports multiple profiles. You can plan your large volume structure in advance.
-
One example is to have Years as folders, with Quarters as sub-folders. Each quarter can have its own storage profile. As part of quarter-end activities, you can activate the storage profile for the next quarter. As an administrator, you can create a folder structure that accounts for years and quarterly time periods within each year.
-
The profiles can also be created in advance. Create the entire structure in advance and activate each quarterly storage profile as needed.
Tip: Profiles can point to network folders.
As an admin, you can create a new storage profile.
-
In the Synergize Enterprise Management Console (EMC), navigate down through tenants and repositories to a specific repository.
-
Select Storage Profiles and Storage.
Result: The New and Activate buttons appear on the screen with the list of storage profiles.
-
To define a new storage profile, click New.
-
Complete the fields in the New Storage Device Profile window. The key information to provide is the location of the physical storage. The dialog describes the only time a local path would make sense: in a deployment where all Synergize components except the client are on the same machine.
-
Click OK.
-
To activate the storage profile, select the profile and click the Activate button.
Tip: Because Synergize connects to the active storage profile device path each time a document is saved, no down time occurs when you want to change an active profile. From that point on, any documents are stored in the newly activated profile device path.
Active, current documents need to be available online. After a set of documents is no longer considered current according to your business rules, you may want to move it to near-line storage.
To move a storage profile device path, follow these steps:
-
Choose any of the following locations for the device path:
-
a file server
-
a network attached storage (NAS) device
-
storage area network (SAN)
-
another valid storage option
-
-
Copy the entire contents of the device path to the new location, drive, or volume for files and folders.
-
Verify the file and folder counts.
-
Ensure that the account running Synergize Services (COM+ objects) has the same rights and access to the new location as it did to the previous location.
-
Modify the profile to point to the new location.
-
Test and verify that you have access to the documents in Synergize.
-
Remove the documents from the old storage location.
Often when you provide access to the user on the machine, the user is not an actual person but an application pool or service account. Setting security for directories with application pools is one example (setting the storage profile device path and not the deployment directories) and using individual application pools for each service or app you need to grant access
-
In Windows Explorer, select the storage profile device path.
-
Right-click to access Properties > Security > Edit > Add > Locations > Select your machine > OK
-
Enter: IIS AppPool\AppPoolName > Check Names > OK
-
Grant all permissions. Allow > Apply > OK
There could be a specific situation where a disk location is local to one Synergize installation but shared with another on a different machine. In such a case, we recommend that you set up the storage location in the following way:
-
On the folder you intend to use as the repository's storage location, right-click and select Properties.
-
On the Sharing tab, select Advanced Sharing.
-
Check Share this folder and click Permissions.
-
Add the computer that hosts Synergize to be able to read and write to this storage location.
-
Click Add.
-
Normally, the only objects that are available are users, groups, or built-in security protocols. To change this, click Object Type.
-
To reduce the search to find only computers, check Computers and un-check all other object types.
-
Update the From this location field, to specify the domain of the Synergize computer. Then enter the actual computer name as an object name.
-
The computer you specified above should have Change and Read access allowed. After you have specific groups or users entered, we recommend you remove Everyone.
-
Ensure that the object also has security access. Note that advanced sharing settings are affected by security settings and vice versa.
-
If you remove access for a computer or user on the Security tab, they will lose access on the Sharing tab.
-
Conversely, if you do NOT share a folder with a computer or a remote user, they will not be able to access the folder on the network (even if they have local security access), by logging in to the computer and using its local resources from their remote location.
-
In Synergize 17.1, you can now specify a document storage profile when adding or saving a document.
Previous Releases: In past releases, document migrations required two major steps and required longer processing time. For example, you are migrating 15 million files to a new AWS S3 cloud container. Using the SPS archive action, you first save the documents to a local active storage profile and then archive them to a non-active storage profile configured for your associated S3 storage destination. In test trials with just 1,000 document files, your process requires 20 seconds per document.
Synergize 17.1: To continue the example above, you specify a destination storage profile directly in the SPS Save Document action. Using SPS and Synergize Explorer 17.1, your test of 1,000 files results in much better performance. Instead of 20 seconds, each document can be saved directly to your S3 storage profile in under 3.0 seconds per document.
This difference is easily demonstrated by comparing the legacy and new strings in the following API POST commands:
Older Releases:
https://<my-synergize-mobile-fleet-server.net>/SynergizeServices/DocumentService/
API/repo1/documents
New Synergize 17.1:
https://<my-synergize-mobile-fleet-server.net>/SynergizeServices/DocumentService/
API/repo1/documents?storageProfileID=MY-NEW-STORAGE-CONTAINER
Tip: Instead of a string, use the integer for your storage profile ID.
-
As an administrator, set up your storage profiles in EMC.
-
In the example image below, the developer has set the content type to application/json and specified their storage profile in the API POST command. The FileName and base64 FileData for the image are also included.
Tip: The query parameter in the request storageProfileId=<number> that selects which storage profile the image file gets stored in is optional. This query parameter can be specified whether you're using the old payload or the new payload. If not specified, the document is saved to the default active storage profile.
Old payload:
multipart/form-data or multipart/mixed with a file section and a properties section
New JSON payload:
{
"FileName": string (the name of the file including the extension)
"FileData": string (the base64 string value of the file)
"Properties": object (the key value pair of the document properties you want to add)
}
-
This example image shows the addDocURL text formatter in Synergize Process Designer.
-
In this example, the new payload data appears in Synergize Process Designer.
-
After running this process, the image is added directly to the storage container and users can make updates in the Queue1 workflow in Synergize Explorer HTML5 edition.

















