INNORIX in Practice, Embedded Web Upload & Download

The file transfer technology of a web service run for ten years has to be replaced.

The service has to keep running.
The customers' work, and the systems the company built, have to stay as they are.

10 YEARS AGO

Enterprise service portal

  • Home
  • Requests
  • Documents
  • My account

Upload documents

Select a file

report.zipBrowse...

Maximum file size: 2 GB

Upload

Supported desktop environment

Where the service began

A limited user environment and data scale

TODAY

Enterprise workspace

My account

Projects / Submit materials

Project #48291

Project materialsAdd files

engineering_data.zip

reference_dataset.tar

Total selected 128 GB
Submit materials

What customers expect today

Many user environments and more complex business needs

In ten years, more than the web service has changed.

Follow how the file transfer technology is replaced while the existing systems stay.

A fictional story of a company modernizing a web service it has run for a long time.

INNORIX in practiceScene 1 / 15

THE TIMELINE10 years ago

10 years agoScene 1 / 15

At the time, the technology was enough.

The company built a system where customers and employees handle their work in one web service.

Customers submit the documents needed, and staff download them to do the work. When the work is done, the results are registered in the web service.

Most files customers submitted then were tens to hundreds of MB.

Customers' environments were fairly limited, too.

ORIGINAL SERVICE ENVIRONMENT

Enterprise service portal

Original release
  • Home
  • Submit request
  • Documents
  • My account

Submit supporting documents

technical_report.zipBrowse...

File size: 128 MB

Maximum file size: 2 GB

Upload document
Customer accounts
1,200
Typical file size
10–200 MB
File transfer screens
4

The development team built the file transfer feature to the company's requirements.

The service ran reliably, and the company kept adding new work to it.

And so ten years passed.

SERVICE STATUSNow

10 years ago

Customer serviceOriginal file transfer

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Launching the first service

Next—

Next story, TodayDeciding to replace →

TodayScene 2 / 15

Customers and their work have changed, but the file transfer technology has not.

Over ten years the company's customer base grew a great deal.

The operating systems and browsers people use to reach the service became far more varied.

What customers submit grew from ordinary documents to design data, video, backups and raw data for analysis.

The development team starts receiving inquiries it never had before.

Development requests

Recent customer feedback
  • Customer supportToday, 09:20

    A customer says they cannot submit files from a new browser.

  • Enterprise salesYesterday, 14:30

    An enterprise customer asked whether they can submit design data of 80 GB or more.

  • Security team3 days ago

    The components and support status of the existing file transfer module need review.

  • Service planningLast week

    Can the new project management service use the existing file transfer feature too?

  • Development teamLast week

    It is hard to tell how a change to the file transfer module affects other business screens.

One way is to keep patching the existing technology for each problem.

But every new environment then needs more development, and every change has to be checked against the other work already running.

Rather than fixing each problem on its own, the company decides to look at replacing the file transfer technology itself.

What the development team has to solve

Keeping existing work running matters more than building new features.

  • Customers' workExisting customers must keep using their accounts and their work.
  • Existing materialsTen years of materials and their download permissions must stay.
  • Business systemsExisting approval, review, analysis and data handling must keep working.
  • Service operationThe replacement must affect customers as little as possible.

SERVICE STATUSNow

Today

Customer serviceRunning as is

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Planning the replacement

NextSurvey the existing environment

Next story, Week 1Surveying the existing system →

Week 1Scene 3 / 15

Find out where the file transfer technology is used.

The team surveys 24 screens and 8 business systems.

At first the development team thought replacing a few upload screens would be enough.

But the survey found the same file transfer technology in employee business systems, partner services and the archive lookup system as well as the customer web service.

Some systems were built to start the next task automatically when a transfer completed.

On some screens the transfer result changed the customer's work status; on others, a security check starts once the file has arrived.

EXISTING SERVICE INVENTORY

File transfer dependencies

File transfer screens
24
Related business systems
8
Registered customer accounts
38,000
ServiceScreensTransfer dependency
Customer portal5Submit materials and download results
Project workspace4Register project materials
Document management3Register and look up documents
Employee workspace4Receive work files and register results
Partner portal3Exchange files with partners
Approval system2Review and approval materials
Document archive2Download past materials
Support portal1Submit support materials

The team studies how each screen selects files, which transfer server it uses, user authentication, storage location, completion events and error handling.

It is not only looking for the code that calls the file transfer feature, but for which business work the transfer technology is tied to.

DEPENDENCY DETAIL

Customer portal / Submit materials

  • AuthenticationExisting customer session
  • DestinationCustomer project storage
  • Access permissionProject membership
  • On transfer completedRegister submitted documents
  • On transfer failedKeep request in pending state
  • Post-transfer processingSecurity inspection
  • Audit recordsEnterprise request history

After the survey, the team sees that the work it must keep is far wider than the technology it must replace.

SERVICE STATUSNow

Week 1

Customer serviceRunning as is

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Dependency analysis
Changes for customers
None

NextSettle the scope

Next story, Week 2Designing the scope →

Week 2Scene 4 / 15

Draw a clear line between what stays and what is replaced.

The development team decided not to rebuild the whole web service.

Existing user accounts, project data, data management and business processes stay in use.

What gets replaced is the technology that selects and delivers files, and the part that connects it to existing business systems.

REPLACEMENT SCOPE

The existing service stays; the file transfer technology is replaced.

BEFORE

  • Customer authentication
  • Project management
  • Business information
  • Existing access policies
  • File transfer componentLegacy file transferExisting integration layer
  • Business processing
  • Document repository
  • Existing customer records

AFTER

  • Customer authentication
  • Project management
  • Business information
  • Existing access policies
  • File transfer componentINNORIXUpdated integration layer
  • Business processing
  • Document repository
  • Existing customer records

A conceptual view of what the existing service must keep and what is replaced.

Here the team focuses less on removing the old technology than on whether the new one produces the same business results as the existing service.

For example, when a customer submits materials, they must be registered to the same project as before.

When a transfer fails, the existing work status must not change by mistake.

Nor may the change let users download materials they are not allowed to.

SERVICE STATUSNow

Week 2

Customer serviceRunning as is

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Integration design

NextDevelopment integration

Next story, Week 3Integrating the first screen →

Week 3Scene 5 / 15

The first file is transferred in the existing web service.

The new file transfer technology goes into the existing web service.

The team chose the most used screen, the customer material submission, as the first to replace.

It does not build a new web service; it applies INNORIX in the existing service's development environment.

The business screen and the way customers enter information stay as they are.

DEVELOPMENT ENVIRONMENT

The same business screen, a new file transfer technology

Existing component

Submit materials

Project #48291

Document category

Engineering data

Description

Updated engineering materials

AttachmentsBrowse...

No file selected

Maximum file size: 2 GB

Submit materials

INNORIX integration

Submit materials

Project #48291

Document category

Engineering data

Description

Updated engineering materials

AttachmentsAdd files

engineering_data.zip

File size 12.8 GB

Transfer completed

Submit materials

The new file transfer technology can now be used in the existing web service.

But the team does not call the replacement done at this stage.

A file arriving correctly and the company's existing work being processed correctly are two different questions.

FIRST INTEGRATION TEST

Test file
12.8 GB
File transfer
Completed
Business integration
Under verification

SERVICE STATUSNow

Week 3

Customer serviceRunning as is

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Validating in development

NextConnect business events

Next story, Week 4Connecting business systems →

Week 4Scene 6 / 15

How will existing business systems understand the new technology?

The team checks that existing work carries on correctly.

In the existing service, when a transfer completes, a business program was built to use the result to register the project materials.

The team writes integration code so the existing business systems can process the new technology’s transfer results.

Rather than changing every business system the company uses, it keeps the existing business call rules wherever it can.

BUSINESS INTEGRATION

The transfer technology changes; the meaning of existing work does not.

EXISTING BUSINESS CONTRACT

Transfer completed

  • Project ID
  • Customer ID
  • Transferred files
  • Storage reference
  • Transfer result

Register project materials

UPDATED INTEGRATION

INNORIX transfer result

  • Request context
  • File information
  • Destination information
  • Completion status
  • Error information

Convert to existing business contract

BUSINESS VERIFICATION

  • Link customer account and filesVerified
  • Register existing project materialsVerified
  • Start security inspectionVerified
  • Notify the person in chargeVerified
  • Change the customer's work statusVerified
  • Record transfer and business resultsVerified

What existing systems expect may differ from what the new technology returns.

The team builds an integration layer to handle those differences and verifies how transfer results affect existing work.

The team does not test only the success cases.

EXCEPTION TESTING

Test conditionExpected business behaviorResult
All files transferredProject materials registeredPassed
Some files failedWork completion heldPassed
Network connection lostTransfer status checked and recoveredPassed
User cancels transferExisting work status keptPassed
Same completion processed againDuplicate registration preventedPassed
User session expiredAuthentication and follow-up per policyPassed
Storage errorMaterial registration heldPassed

In particular, the team verifies the existing business logic so that work never starts wrongly when a completion is processed twice or only some files arrive.

SERVICE STATUSNow

Week 4

Customer serviceRunning as is

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Integration testing

NextCompatibility validation

Next story, Week 5Validating data and environments →

Week 5Scene 7 / 15

Files submitted ten years ago must still download.

Past materials and today's customer environments are checked.

The team has finished testing transfers of new files.

But the company's customers do not use only new materials.

They reopen materials from projects finished years ago, or download results delivered in the past.

Existing materials must stay usable after the replacement.

Document archive

Compatibility testing

Ten years of materials

CreatedFileSizeDownload test
10 years agooriginal_documents.zip128 MBVerified
8 years agoproject_report.pdf42 MBVerified
6 years agoreference_materials.zip840 MBVerified
3 years agoengineering_archive.zip1.8 GBVerified
Last monthproject_update.zip1.4 GBVerified
Todaynew_engineering_data.tar12.8 GBVerified

HISTORICAL DATA VERIFICATION

  • Actual storage location of existing filesChecked
  • File names and formats of existing materialsChecked
  • Download permission per materialChecked
  • Existing encryption and compression formatsChecked
  • Links between past projects and materialsChecked

If existing materials can be read as they are from the current storage, there is no need to move every file to new storage.

But if a storage format or encryption can only be used by the old technology, a separate conversion and compatibility plan is needed.

The team checks the structure of the real materials before deciding how to keep them.

Customers' environments are validated too.

CLIENT ENVIRONMENT VALIDATION

Operating systemBrowserUploadDownload
WindowsChromeVerifiedVerified
WindowsEdgeVerifiedVerified
macOSSafariVerifiedVerified
macOSChromeVerifiedVerified

A fictional operating environment this company validates in its project. The test targets are set to the actual support scope.

The team also checks security software, network policies and installation restrictions at enterprise customers, and whether the new technology can coexist with existing modules.

This is to make sure no customer loses access to the service during the replacement.

SERVICE STATUSNow

Week 5

Customer serviceRunning as is

Share of new transfers

0%

INNORIX

Existing technology 100%

Team's current work
Preparing the launch
Changes for customers
None

NextLimited rollout

Next story, Week 6Applying to some customers →

FIVE WEEKS LATER

Validation in the development environment is complete. But customers are still using the existing service.

Production service

Operational
Requests received today
684
Transferring now
47
In processing
213
ProjectCurrent activityTransfer technology
#48291Uploading project materialsExisting component
#48292Downloading resultsExisting component
#48293Submitting documentsExisting component
#48294Employee file downloadExisting component

Now the new technology has to go into the live service.

The replacement starts while work and transfers already in progress are protected.

INNORIX in practiceScene 1 / 15

THE TIMELINE10 years ago

Week 6Scene 8 / 15

Not every customer’s file transfer technology changes at once.

The first transfers start in production.

To see the many situations a live service can produce, the team decided to apply the new technology first to a limited set of customers and work.

The web service controls which requests use it, so the existing and new technologies can coexist for a while.

Customers using the same service may use different file transfer technologies depending on whether they are in the validation group.

CONTROLLED PRODUCTION ROLLOUT

It starts with 10% of new transfer requests.

  • Existing file transfer technology90%
  • INNORIX10%

Applies to new transfer requests only

Transfers already started finish on the existing technology.

CustomerTransfer requestAssigned technology
Company AExisting transfer in progressExisting component
Company BNew requestINNORIX
Company CNew requestExisting component
Company DNew requestINNORIX

This approach assumes an environment where the existing and new technologies run side by side.

Data already in transfer is not moved to the new technology mid-way; the scope is decided from new transfer requests onward.

The team watches the transfer and business results of customers on the new technology separately.

SERVICE STATUSNow

Week 6

Customer serviceIn service

Share of new transfers

10%

INNORIX

Existing technology 90%

Team's current work
Limited rollout
Changes for customers
File transfer for some customers

NextReview production results

Next story, Week 6, 10:32First request on the new technology →

Week 6, 10:32Scene 9 / 15

A real customer makes the first request with the new technology.

The first customer on the new file transfer technology signs in to the web service.

They open the project screen they have always used and submit new materials.

Nothing changed: not the project number, not the account, not the way work is requested.

Enterprise workspace

Company B

Projects / #48302 / Submit materials

Submit updated project data

PROJECT MATERIALS

  • File nameSize
  • updated_design.zip18.4 GB
  • technical_specifications.pdf86 MB

Transfer progress 100%

Materials submitted successfully

PROJECT ACTIVITY

  • 10:32 Materials submission started
  • 10:41 All files received
  • 10:42 Project materials registered
  • 10:42 Technical review team notified

The company's staff check the submitted materials in the existing business system.

They do not need to know which file transfer technology the customer used.

The team confirms the first real request did not end at "transfer complete" but carried through to the existing business system.

SERVICE STATUSNow

Week 6, 10:32

Customer serviceIn service

Share of new transfers

10%

INNORIX

Existing technology 90%

Team's current work
Limited rollout
Changes for customers
File transfer for some customers

NextReview production results

Next story, Week 7An unexpected problem →

Week 7Scene 10 / 15

A problem not seen in the development environment appears.

A particular work environment turns up, and the scope is adjusted.

A replacement project does not always go to plan.

While watching real customers' work, the team found that one partner system handled transfer completion results differently from the others.

The transferred files were fine, but some information the existing registration program needs was not converted correctly during integration.

PRODUCTION COMPATIBILITY ISSUE

The files arrived correctly, but the business registration did not complete.

TRANSFER RESULT

Completed

Request #48324

4.2 GB

Received files verified

BUSINESS RESULT

Registration pending

Partner workspace

Required legacy reference not mapped

DEVELOPMENT INVESTIGATION

ItemInvestigation result
File receivedVerified
File integrityVerified
Project informationVerified
Legacy partner referenceMapping required
Business registrationPending

ROLLOUT DECISION

Further rollout for this work is put on hold.

Materials already received are kept and the registration data is restored. New transfers for this work use the existing technology until validation is complete.

The team decides to fix this work type before widening the new technology’s scope.

Rather than re-sending files already delivered, it first checks the stored materials and the work status.

It fills in the missing business information, makes sure nothing is registered twice, and carries on with the existing work.

After the fix

RESOLUTION RECORD

TimeActivity
10:12Registration delay found
10:20Further rollout for this work held
10:35Reference data the existing system needs confirmed
11:10Integration data handling fixed
11:40Registration restored from the received files
14:20Same work type validated again
Next dayNew technology resumed for this work

A system run for ten years can hold undocumented dependencies and exception handling.

So a replacement project needs not only validation of the new technology, but also a way to check how existing work really behaves and to respond safely when something goes wrong.

SERVICE STATUSNow

Week 7

Customer serviceIn service

Share of new transfers

10%

INNORIX

Existing technology 90%

Team's current work
Extra validation
Affected work
1 partner registration

NextFix and revalidate

Next story, Week 8Widening the scope →

Week 8Scene 11 / 15

The scope widens, starting with validated work.

The new technology goes to validated work first.

The partner work where the problem appeared has been validated.

The team widens the kinds of work and the customers that use the new file transfer technology.

Now it is used not only for customer submissions but for employee work downloads, project result registration, archive lookups and more.

ROLLOUT PROGRESS

The replacement scope is widening.

Business systemScreensRollout status
Customer portal5Applied
Project workspace4Applied
Document management3Validation completed
Employee workspace4Applied
Partner portal3Limited rollout
Approval system2Validation completed
Document archive2Applied
Support portal1Applied

The team does not look at transfer success rates alone.

It also checks that customers' real work is processed as before, that inquiries do not rise, and that registration and access permissions stay correct.

Rollout simulation

PRODUCTION TRANSITION

  • Wk 6
  • Wk 8
  • Wk 9
  • Wk 10

Existing technology

50%

By new transfer requests

INNORIX

50%

By new transfer requests

Kept throughout

Customer accounts, project data, existing materials, business processes, access permissions

Customer web service

Operational

The scope widens, starting with validated work.

SERVICE STATUSNow

Week 8

Customer serviceIn service

Share of new transfers

50%

INNORIX

Existing technology 50%

Team's current work
Staged expansion

NextPrepare full rollout

Next story, Week 10Replacement complete →

TEN WEEKS LATER

The technology replacement for new file transfer requests is complete.

Every new transfer now uses the new technology.

Screens replaced
24 / 24
Existing service screens
Business systems connected
8 / 8
Existing work environment kept
Share of new transfers
100%
INNORIX

Production verification

Final rollout
  • Existing customer accounts and authenticationVerified
  • Existing projects and business dataVerified
  • Existing material downloadsVerified
  • Business system integrationVerified
  • File upload and downloadVerified
  • Transfer failures and exceptionsVerified
  • Access permissions and security policiesVerified

Customer service Operational

On the day the replacement completes, customers sign in and work as usual.

INNORIX in practiceScene 1 / 15

THE TIMELINE10 years ago

A month laterScene 13 / 15

Now the old file transfer technology can be removed.

The operational dependencies on the old modules are removed.

Even after the new technology handled every new transfer, the team kept the old technology for a while.

Unexpected business dependencies might remain, or long transfers started on the old technology might still be running.

After a period of operation confirms the old technology is no longer used, removal begins.

LEGACY COMPONENT DECOMMISSIONING

The technology used for ten years is retired.

Active transfers on the old technology
0
Screens calling the old module
0
Decommissioning taskActionStatus
Legacy upload moduleRemoveCompleted
Legacy download moduleRemoveCompleted
Obsolete client resourcesRemoveCompleted
Unused integration codeRemoveCompleted
Historical transfer recordsRetainCompleted
Existing customer documentsRetainCompleted
Previous configuration backupArchiveCompleted
Recovery procedureDocumentCompleted

Removing the old technology does not delete past customer materials or work history.

The team cleans up program components, code, settings and server resources no longer in use.

Operating records and existing materials that must be kept stay, under the company's retention policy.

SERVICE STATUSNow

A month later

Customer serviceIn service

Share of new transfers

100%

INNORIX

Existing technology 0%

Team's current work
Clean-up complete

NextWatch operations

Next story, 6 months laterTaking on new work →

6 months laterScene 14 / 15

Customers start sending materials that were hard to submit before.

Work that used to be limited is now handled in the service.

After the replacement, the company's service planning team revisits customer requests from the past.

Some work had been hard to offer in the web service because of data size or customer environments.

Work such as design data analysis and review of large raw datasets.

The company widens what the existing service does.

NEW BUSINESS REQUESTS

The existing web service handles work at a new scale.

ProjectBusiness typeData sizeStatus
#51201Document review128 MBCompleted
#51202Engineering evaluation84 GBUnder review
#51203Original data analysis320 GBProcessing
#51204Technical consultation2.4 GBCompleted
#51205Design data verification128 GBReceiving
#51206Research data processing1.2 TBProcessing

A customer from ten years ago and a new customer use the same service.

EXISTING CUSTOMER

Company A

Customer since original launch

Archived project documents

128 MB

Download documents

Looking up materials registered ten years ago

NEW CUSTOMER

Company Z

Recently registered customer

Original research dataset

1.2 TB

Submit materials

Submitting large new work materials

Work from different eras happens in the same service.

The company keeps past materials for existing customers while giving new customers the environment they need.

It is built so that the service's history and existing work never stand in the way of new technology.

SERVICE STATUSNow

6 months later

Customer serviceIn service

Share of new transfers

100%

INNORIX

Existing technology 0%

Team's current work
Expanding to new work

NextImprove the service

Next story, A year laterA new developer's first day →

A year laterScene 15 / 15

A new developer joins the development team.

A new developer extends the existing service.

A new developer is given the task of adding a new business feature for partners to the existing web service.

In the past, building a new screen meant understanding how the old file transfer module behaved and all its exception handling.

Now the team has a common integration approach and development documents for applying file transfer to business systems.

Internal developer documentation

File transfer integration
  • Getting started
  • Upload integration
  • Download integration
  • Authentication
  • Business events
  • Error handling
  • Security policies
  • Testing requirements

Add file upload to a new service

Apply file upload to a new business screen using the company's common file transfer integration module.

APPLICATION CONTEXT

  • Customer authentication
  • Project reference
  • Business request type
  • Authorized destination
  • Transfer completion handling

Integration requirements

Use the existing authentication, registration, error handling and business event rules.

INNORIX developer documentation

The new developer uses the integration approach the company defined, with no need to relearn and rebuild every internal detail of the old technology.

Using the company's development documents and the INNORIX developer documentation, they build the file transfer the new service needs.

The web service run for ten years keeps evolving.

The replacement was not the end of a project but a new foundation for the development ahead.

SERVICE STATUSNow

A year later

Customer serviceIn service

Share of new transfers

100%

INNORIX

Existing technology 0%

Team's current work
Continuous development
Existing customer materials
Still available

NextNew business development

FROM THE ORIGINAL RELEASE TO TODAY

Ten years of the web service did not disappear.

Service environmentBefore replacementAfter replacement
Customer accountsExisting accountsKept
Past projectsExisting projectsKept
Accumulated materialsExisting storageKept after validation
Business processesExisting systemsKept
Security and access policiesCompany policiesKept and revalidated
File transfer technologyLegacy componentINNORIX
Integration approachSeparate implementationsNew common integration
New feature developmentOld technology baseNew technology base

The company applied new technology while keeping the service and the customer experience it built over ten years.

The graph is a conceptual view of the service’s continuous growth.

MODERNIZE THE TECHNOLOGY. PRESERVE THE BUSINESS.

A service run for ten years holds value that technology alone cannot explain.

The materials customers built up, the processes the company created,

and the many systems and lessons that come from years of operation.

WHAT REMAINS

What the company built

  • 38,000 customer accountsThe relationship with customers
  • 10 years of documentsAccumulated customer and business materials
  • 8 business systemsThe company's work environment
  • 24 existing screensHow customers and staff work

WHAT CHANGES

The technology newly applied

  • INNORIXEmbedded file transfer
  • Upload & DownloadA new file transfer environment
  • Business integrationConnected to existing and new work
  • Future developmentThe technology base for services to come

Replacing file transfer technology does not mean rebuilding everything the company has built.

The technology it needs can be modernized while the existing work environment stays.

Keep the last ten years of the service, and prepare for the next ten.

INNORIX

The technology behind this story

Embedded Web Upload & Download

Professional file transfer technology for newly built web services and for web services and software a company has run for years. It integrates file upload and download with the business systems and user environments the company already has, and supports new data scales and business needs.

View the product