Duet Enterprise Configuration in Production

[Former Member]

Hi All,

I would like to know, what are the things that we need to keep in mind while configuring Duet Enterprise in production.

As we know there are a few settings which are stored in transport requests , while majority of tasks need to be done manually.

What would be the best approach to configure Duet Enterprise in production?

[Former Member · Accepted solution]

Hi Meghna,

I'm currently involved at customer premisse to configure Duet Enterprise throughout the whole landscape: started with development, next integration/test, QA and ultimate production.

The approach we follow(ed) is to first entirely setup the development environment; test/validate it: Duet Enterprise runtime and designtime.

And next use the GW system of the Dev environment as baseline for the other environments; through SAP system copy. In the other environments it is then sufficient to only configure the environment settings: RFC connections, trust/sso with the backend(s), SharePoint certificate imports, refresh endpoints of standard Duet Enterprise business scenario's; and of course the connected [existing] backends must still be configured for communication with the GW-system (RFC connection for workflow and reporting publication)

We can apply this approach because we are installing Gateway on fresh SAP NW installations/systems.

In case you are adding Gateway / SAP Add-On of Duet Enterprisee to existing system, there is no other option as to manually repeat the entire Duet Enterprise configuration per environment.

Regards, William.

[Former Member · Accepted solution]

Hi William,

Thanks for the reply!

We would also be working with fresh GW systems in our scenarios.

It looks like a good option.Did you face any challenges because of following this approach?

Thanks ,

Meghna

[Former Member · Accepted solution]

Hi Meghna,

we faced one issue with the first 'system copied' system that we restored; from Dev to Test.

After correcting the RFC Connections and so in Test for this environment; still the GW system on Test internally had some [internal] connection to the source Dev environment --> WSIL connection.

The fix was to update "icm/host_name_full" profile parameter with the server name of the Gateway Test system.

Hint; another sympton of this [in]correct hostname is detectable through SOAMANAGER:

-Start SOAMANAGER

-Management Connections

-Maintain new Connection --> check the default filled in hostname ==> should be of the current GW system.

Regards, William.