Storage (STORE)

Storage objects allow you to upload a file and store it in binary format in the database. On the Storage page you specify files that you want to store in the object. You can add, edit or remove files. Once a storage object definition is saved, all uploaded files are permanently stored in the database with the object. Even if you delete a file from the table on the Storage page of the object definition, the files are kept. This is important for rollbacks and historical data.

Typical Use Case

STORE objects are useful when you need to make the same file, such as a script, executable, or application, available to multiple Agents without manually deploying it on each one.

For example, suppose you have an application (such as a compression or decompression utility) that must be used by Jobs running across hundreds of Agents. Instead of installing this application on every Agent, you can upload it once to a STORE object.

In your Job definitions, reference this STORE object in the script on the Process page using the :ATTACH_RES statement (for example, :ATTACH_RESObjectName, ResourceName, [Usage], [Variable]) and add any necessary arguments. During execution, the Job automatically retrieves the file from the STORE object, ensuring that all executions use it across all Agents.

This centralized approach simplifies maintenance, ensures consistency, and streamlines updates for shared files used throughout your automation environment.

See also :ATTACH_RES.

1. In the Process Assembly perspective click Add Object and add a Storage object. For more information, see Adding Objects.

   A Storage object definition is made up of the following pages:

   • Standard pages that are always available, no matter what type of object you are defining:

     • Defining the General Page

       Defining the Version Management Page

       Defining the Documentation Page

     The object-specific page described here.

2. On the Object Name dialog enter the name of the new object. Choose it carefully. For more information, see Best Practices: Naming Conventions for Objects.

3. Click OK to open the object definition pages.

4. On the Storage page click the first row in the list to activate it and enter the Name of the file you want to store in the database. The combination of Name and Operating System must be unique.

5. In File Upload click the upload icon and search for the file to upload it.

6. The file format of the selected file is displayed in Type, it can be Binary or Text. This ensures that the code page settings of the target system are applied.

7. Optionally, enter the Version number of the file. This information helps you keep track of its changes.

8. Optionally, enter the Operating System from which the file originates. The options are:

   • Windows

   • Unix

   • * (any Operating System)

9. Optionally, enter the Platform from which the file originates, where * means any Operating System.

10. Optionally, enter information on the Hardware , where * means any hardware type.

11. Save your changes.

Notes:

• Maximum file size: 95 MB (99900000 bytes).

  Administrator users can reduce the size by setting the storage size with the MAXIMUM_STORE_RESOURCE_SIZE key in the UC_SYSTEM_SETTINGS system variable to a lower value. For more information, see UC_SYSTEM_SETTINGS - Systemwide Settings.

• The Operating System, Platform, and Hardware values apply only when files are transferred to the Agent of the operating system. This kind of file transfer is executed with an :ATTACH_RES statement in the transfer script. For more information, see :ATTACH_RES.

Upon installation, the Automic Web Interface automatically loads standard plug-ins from its internal folders. To extend the functionality of your environment with additional plug-ins, bundles, or solutions, , or content from the Broadcom Support Portal, administrators must use a specialized Store object.

The UC_ECC_PLUGINS Store object is delivered by default in Client 0 and resides in the DIV_VARIABLES folder. It serves as the master manifest for which bundles are enabled for users and is read by the system during every login process.

• Installation & Updates: When you upload new plug-in files to this object and save it, the related features are installed and become available to users at their next AWI login.

• Removal: If a file is removed from the list in UC_ECC_PLUGINS, the related plug-in is no longer loaded or accessible after the user's next login.

Administrators can modify the contents of this object but cannot delete the object itself.

Users must have Read (R) rights to the UC_ECC_PLUGINS object. Without these rights, users can only see standard definition pages (like General, Version Management or Documentation) for associated objects; they will not be able to see object-specific pages, such as the Web Service page for WebService Jobs.

Plug-ins managed within this object are synchronized across the AWI environment. Success is verified when the new object-specific pages or menu options appear in the interface after a fresh login.

The UC_TRUSTEDCERTS storage object is delivered by default with Client 0 and it is stored in the DIV_VARIABLES folder. It allows you to save the certificates that the Agents need in the Automation Engine.

You can also use it to store the certificates required for the LDAPS and the Automation.AI connection.

This object is empty by default. To load the relevant certificates do the following:

1. Go to the DIV_VARIABLES folders and open the UC_TRUSTEDCERTS storage object.

   You can also use the search bar to search for the object. For more information, see Using the Global Search for Objects and Tasks.

2. On the Storage page, add a new row and enter a Name for the certificate that you want to upload.

3. On the File Upload column, click the upload button.

4. In the windows that opens, navigate to the location of the certificate that you want to updated and select it to upload it.