Beta Testers Wanted - RA REST Replacement

[Kaj Wierda]

We have been working on a new version of RA REST and this agent includes many enhancements:

• 100% backward compatible with original RA REST
• Easy setup (no DBLoad required)
• Up-to-date 3rd party libraries
• Support for REST verbs CONNECT, PATCH, and TRACE
• Bearer token authentication
• Can ignore certificate errors when connecting to REST endpoint
• Include/exclude headers in log
• New retry feature to replace status polling constructs (greatly reduces number of executions!)

To ensure this new agent is backward compatible with existing REST jobs, we are looking for customers to participate in our validation program. Please contact us at [e-mail]

------------------------------
Kaj Wierda
Sr. Product Line Manager | Automation

Broadcom Software
------------------------------

[Michael A. Lowry]

We are interested.

[Christian Schmitt]

Hi Kaj, 

we are interested too :) 

[Thierry Verreyt]

Hi,

We are also interested. 

What are the requirements to install this beta version?

[Michael Dolinek]

Hi @Thierry Verreyt

the minimum requirements are

• AE and AWI v21.0.8 or higher for IG REST v21
• AE and AWI v24.1 or higher for IG REST v24
• Java 11 or higher for IG REST v21 or v24

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------

[Jared Kessans]

Can this be ran in parallel with the current REST agent?

[Michael Dolinek]

Hi @Jared Kessans

Yes, the existing RA REST solution and the new Integration REST can run in parallel. The Integration REST can execute/use all existing objects BUT after installing IG REST any newly saved REST-object (JOBS, CONNECTION) cannot be executed/used by an (old) RA REST Agent.

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------

[Leon Carroll]

Hello, I'm interested.  I'm currently running 24.2 in development.

[Keld Mollnitz]

Hi @Michael Dolinek,

you wrote "...any newly saved REST-object..." but did you mean "...any newly created REST-object..." ??

/Keld.

[Michael Dolinek]

Hi @Keld Mollnitz

with the term "any newly saved REST-object" I wanted to cover these two cases

• a new REST-object was created,  edited and finally saved
• an existing (old) REST-object was opened, modified and then saved

In both cases the saved object include data that cannot be handled by the old RA REST agent.

Any other unmodified old REST-object can still be used by the old RA REST agent.

I hope this makes it clear for you!

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------

[Keld Mollnitz]

Hi @Michael Dolinek

what are the fallback options, if any ?

/Keld.

[Michael Dolinek]

Hi @Keld Mollnitz

If I understand you correctly, you want to make sure that the old RA REST can use/execute these objects. Therefore, I would do the following:

1. export the objects one by one in JSON or XML format
2. remove all the "new" attributes/fields/properties in the text-files using a text-editor
3. renaming the original objects in the AE
4. try to import the modified files
5. check/verify that these objects can be used/modified/saved/executed

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------