Skip to Content

Packaging gateway service, should I exclude the service defined in /n/iwfnd/maint_service?

We have had a really tough time deleting the service from /n/iwfnd/maint_service.

The service was transported from a transport of copies of our gateway package ( ZAPMEXTERNALDATA ).

I'm wondering if the problem is that we shouldn't have transported that service.

When we created the service in /n/iwfnd/maint_service maybe we should have made it a local object so it wouldn't get transported as part of our ZAPMEXTERNALDATA package?

Then the customer would just install our package and then browse for the service and configure it in /n/iwfnd/maint_service.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 19, 2017 at 02:43 PM

    I usually transport the registration and never had any issue. Once the transport happens, you just have to change the system alias to point to the right backend system. Why did you try deleting the registration?

    Add comment
    10|10000 characters needed characters exceeded

    • I guess what we hit was as follows. We didn't know much about embedded vs. hub deployment etc.

      We ended up having the customer import our gateway package ( entitysets, etc ) into the hub.

      I think eventually we figured out that what we wanted was to have the gateway package in the backend system, and the hub wouldn't contain anything ( it would just browse for the service on the backend system ).

      But then we couldn't browse for the service on the backend system since it was already in the list.

      I don't know if it would have worked if we just had them change the system alias on the registration.

      I guess my concern is that it seems bad to send stuff to customers that they are unable to delete. I eventually figured out how to do the delete by changing the scrsystem on a couple of TADIR objects but it was quite painful.