cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

FAQs: FlexNet Operations Software Delivery (ESD) – FTP/SFTP File Uploads

FAQs: FlexNet Operations Software Delivery (ESD) – FTP/SFTP File Uploads

Last Update: 2024-06-12

FlexNet Operations Software Delivery (ESD) supports uploading file images to the upload server using FTP/SFTP.

FlexNet Operations Software Delivery (ESD) is scheduled to move to the new infrastructure on June 2, 2024. As part of that move, changes to the FTP/SFTP file upload functionality will be required.

Starting June 2, 2024, transferring files directly to the root directory will be discontinued and producers will need to transfer files to the upload sub-directory under the root directory.

To assist with preparing Software Delivery (ESD) producers with the upcoming change, we’ve provided a list of FAQs. If you have any questions that are not covered in this list, please contact Revenera Technical Support or your trusted Revenera contact for further assistance.


What is changing in Software Delivery (ESD)?

FlexNet Operations Software Delivery (ESD) in Production is scheduled to migrate from the Revenera Data Center to the new AWS environment on June 2, 2024. As part of this migration, transferring files directly to the root directory or existing sub-directories (excluding the /upload directory) using FTP/SFTP will no longer be supported.

Will existing Software Delivery (ESD) data be migrated?

Yes; files and sub-directories (including their contents) that exist in Software Delivery (ESD) Production will be migrated to the new AWS environment.

Note: Producers can continue to create new sub-directories under root until May 31, 2024. These sub-directories will be migrated to the new AWS environment but will not be accessible.

How does this affect existing Software Delivery files and/or sub-directories in Production?

Existing files and sub-directories under the root directory in Production will be migrated to the new AWS environment on June 2nd; however, Producers will not be able to make edits under the root directory.

Please refer to the table below for more details:

  Pre-Migration Post-Migration 
  Under Root Directory

Under a Sub-Directory

(including upload directory)

Under Root Directory

Under a Sub-Directory

Under /upload directory

Existing Files (created before migration)  
Existing files available for use Yes Yes No No Yes
Edit or remove existing files Yes Yes No No Yes
           
Existing Sub-Directories (created before migration)  
Existing sub-directories available for use Yes Yes No No N/A
Edit or remove existing sub-directories Yes Yes No No N/A
           

 

How does this affect new Software Delivery files and/or sub-directories in Production?

New files and sub-directories cannot be created directly under the root directory. New files and sub-directories can be created under the upload directory.

Please refer to the table below for more details:

  Pre-Migration Post-Migration
  Under Root Directory

Under a Sub-Directory

(including upload directory)

Under Root Directory

Under a Sub-Directory

Under /upload directory

New Files (created on or later than June 2nd)  
Create new files N/A N/A No N/A Yes
Edit or remove files N/A N/A No N/A Yes
           
New Sub-Directories (created on or later than June 2nd)  
Create new sub-directories N/A N/A No N/A Yes
Edit or remove sub-directories N/A N/A No N/A Yes
           

 

How to prepare for the upcoming change?

  • If the Software Delivery integration uploads files directly under the root directory or to an existing sub-directory (with exception of /upload directory), producers should take the following steps:
    • Discontinue uploading files directly under the root directory or sub-directory under root directory.
    • Change the file upload process to transfer new files to the upload directory.
    • Update the file retrieval path in Software Delivery integration to the upload directory under the root directory (see examples below).

For ALM:

Using Data Import Template: Update the ‘RetrieveFromLocation’ in the Load File Image data import template with the relative path to the file in the upload directory: upload/filename

ESDDataImportTemplate.png

 

Using Web Services: Update the ‘RetrieveFromLocation’ in the uploadFile web service with the full path to the file in the upload directory: upload/filename. Refer to the FlexNet Operations SOAP Web Services documentation for more information.

ESDWebService.png

 

For LLM: 

Using Converter Templates/Batch Transaction: Update the ‘RetrieveFromLocation’ in the Load File Image transaction file with the relative path to the file in the upload directory: upload/filename

ESDConverterTransactionTemplate.png

 

ESDWebService.png

 

Labels (2)
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jun 12, 2024 06:15 PM
Updated by:
Contributors