Open Documentation Menu

How do I handle hooks in a cloud migration?

Overview

This section tells you what you need to know when analyzing hooks in on-premises systems for transfer to the cloud.

Prerequisites

You require access to hook files.

This is how it works

You can continue using hooks in the cloud. In a private cloud, you can use Groovy hooks with limitations or webhooks. In a public cloud, this is done using webhooks.

Alternatively, you can also configure many scenarios using d.velop custom logics. Existing hooks cannot simply be carried over; rather they must be checked and transferred individually.

Ideally, the analysis will be carried out by Consulting employees who have the relevant hook knowledge.

Possible strategies for working with hooks:

  • Do away with the hooks by configuring the Customizing scenario using d.velop custom logics and d.velop business objects

  • Analyze and convert the hooks to webhooks

Keep the following in mind when analyzing the hooks:

  • Are the hooks JPL or Groovy hooks?

  • Are DLL, EXE or other files or applications executed? If yes, check their functions and mappability in the cloud.

  • Are file operations used (write file, read file, etc.)? File operations are no longer possible. Check whether these file operations are necessary or whether alternatives exist.

  • Are database queries executed? If yes, keep the following additional aspects in mind:

    • Which database tables are used and which information is collected? Can the information from the database query also be queried using the DMS API? Are there any limitations?

    • Are customer-specific database tables used that do not match the standard d.3 scheme? You can use custom database tables in d.velop business objects and call them using hooks.

  • Which entry points to the rendition service are used? Rendition hooks can no longer be used in the cloud.

  • Are dataset hooks used? If yes, could these dataset hooks be mapped with d.velop custom logics so that the hook is no longer needed?

  • Are master data validations used (for example in the hook insert_entry_10)? If yes, could these master data validations be mapped with d.velop custom logics so that the hook is no longer needed?

  • Are other systems accessed (SAP, NAV, etc.)? If yes, can these systems also be reached via the Internet?

  • Are functions mapped that exist but are not currently used?

  • Are functions mapped that are currently used but that would become obsolete after a cloud migration (e.g. contract management hooks)?

  • Are there other functions that cannot be mapped in the cloud?