Webinar (on-demand): OutSystems and Analytics Integration: A New Strategy to Reduce Costs

Discover everything you need to know about Hubway Connect

Try the product online without any installation or purchase commitment
Hubway Connect

Innovative ways to leverage your data for business outcomes

Find out how Hubway Connect can help you get more value from your OutSystems platform
Hubway Connect

Learn and expand your Hubway Connect knowledge

Deep dive in articles, videos and technical information to maximise its use
Hubway Connect

Start free and expand without surprises

Choose the Hubway Connect offer that best meets your needs and suits your budget
Hubway Connect

We are here to help. Let’s talk.

Connect with us via your preferred channel and we will be happy to answer your questions
Hubway Connect
  1. Home
  2. Knowledge Base
  3. FAQs
  4. Hubway Extract
  5. Hubway Extract – Support Contents – S3

Hubway Extract – Support Contents – S3

Q: Does Hubway Extract create the S3 Bucket automatically if it doesn’t exist? 

A: No. One precondition for the connection to work is that the S3 Bucket must already exist in your AWS account. If the bucket does not exist, the connection will fail.

 

Q: What file formats are generated in S3? 

A: Hubway Extract generates .json files containing the extracted entity data and an .xml file containing the project metadata.

 

Q: How do I prevent my files from being overwritten with every new synchronisation? 

A: When configuring the connection, it is crucial to correctly define the “File Path Template”. If you do not define a project or a unique identifier (like a timestamp) in the path, the document may be overwritten with each synchronisation. The default suggestion is to use {Project}/{Entity}_{Timestamp}.json to ensure separation of history and files.

 

Q: What AWS permissions do I need to provide to Hubway Extract? 

A: You need to provide credentials (Access Key and Secret Key) that have permission to write to the chosen S3 Bucket and list/open objects.

 

Q: Can I change a Plan’s connection type (e.g., from SQL Server to S3) after it is created? A: Yes, but only while the plan is not yet published. Once the plan is “Published,” the connection type is locked to maintain history consistency and traceability. You can still edit the credentials or point to a different bucket (within the same S3 type), but you cannot swap the connection technology.

 

Q: What happens if I run a “Full Sync” again for the same file? A: Running a new Full Sync replaces the existing file in S3 with a fresh version. This ensures you always have the most up-to-date “snapshot” of your data, without duplicating old records in that file.

 

Q: How are files and folders named in S3? 

A: The folder structure is automatically derived from the project’s Service Name. The files follow the Entity name (or its Alias, if configured), ensuring that the organisation in S3 mirrors exactly the structure defined in Hubway Connect.

 

Q: How are S3 bucket names configured and managed? 

A: Bucket names are configured directly within the connection settings. You can update them, but no other checks are made, so when an invalid bucket is defined, the connection will fail. Always specify the correct Bucket Name from your S3 server, along with the other connection parameters, to ensure the connection is established correctly.

 

Q: What time zone is used in the extracted files? 

A: All date and time values are stored in UTC. This is a native product standardisation to avoid timezone inconsistencies between the source server, the Hubway server, and your Data Lake/S3.

Was this article helpful?

Need Support?

Can't find the answer you're looking for?
Contact Support