What is the Altinn 3 Broker Transition Solution For broker service owners whose end users are reliant on using Altinn 2, but who wish to migrate their broker service to Altinn 3, Altinn is offering a Transition service. This enables communication between senders and receivers of files regardless of which Altinn Broker service they are integrated to.
This service will allow service owners to link an existing Altinn 2 service to an Altinn 3 resource, and to forward Altinn 2 Broker Service requests to the Altinn 3 Broker Service app while not substantially changing the Altinn 2 Broker Service End User experience. »
ServiceOwners In order to use the Broker Transition solution in Altinn 2 to create, upload and retrieve file metadata, a service owner must complete the following steps.
Have an existing Altinn 2 Broker Service. Have or create a corresponding Altinn 3 Broker Resource. See how to get started with Altinn Broker here. Request a transition setup from the Altinn 2 Service to the Altinn 3 Resource. Determine the date for when this should go live. »
About The Altinn 3 Broker Transition service bridge is an internal component in Altinn 2 that transfers Broker requests from Altinn 2 to Altinn 3 for a given request, based on the ServiceCode/ServiceEditionCode combination of the request. This is an implementation of the soft shift solution described here.
Technical overview Altinn 2 allows end users in Altinn 2 to make BrokerService requests for specific Broker Services that will be transferred to Altinn 3 instead of being stored in Altinn 2. »
These pages describe the difference in usage between existing Altinn 2 Broker Service and Altinn 3 Broker Transition operations.
Usage RestDifference in Rest operation usage between Altinn 2 and Altinn 3 transitioned services.
Usage SOAPDifference in SOAP operation usage between Altinn 2 and Altinn 3 transitioned services. »
Difference in usage between existing Altinn 2 Rest Operations and Altinn 2 Rest operations that have been transition to Altinn 3. For standard usage of Altinn 2 Rest operations, see [Altinn Docs (norwegian only)] (https://altinn.github.io/docs/api/rest/formidling/)
For all Altinn 3 transitioned services, Receipts will be pseudo-receipts generated from the Altinn 3 file metadata. This means all receipts returned will be pseudo-receipts, and all receiptIds will be 0.
If your use case requires receipt usage, please submit a feature request. »
Difference in usage between existing Altinn 2 SOAP Operations and Altinn 3 SOAP operations that have been transition to Altinn 3. SOAP operations for Altinn 2 Broker Service are spread over 3 endpoints. For most requests there will be no functional difference between Altinn 2 and Altinn 3 requests.
Service Endpoint Description BrokerService Service WS Handles metadata requests. Service Basic Service EC BrokerService Streamed Streamed WS Handles file data requests. Streamed Basic Streamed EC Receipt Receipt WS Handles receipt requests. »
About Altinn 3 Broker Transition SolutionWhat is the Altinn 3 Broker Transition Solution
Getting started with Altinn Broker Transition SolutionHow to get started using the Broker Transition solution from Altinn 2 to Altinn 3
Technical OverviewThe Altinn 3 Broker Transition Solution allows service owners who own broker services in Altinn 2 to point those services towards Altinn 3 using an internal Altinn 2 bridge.
UsageHow to use the Altinn 3 Broker Transition solution. »
