[Apiman-user] export/import data config in apiman

[Balu S]

Further to this email.

The export/import tool provided in Apiman manager seems not complete. After
I have imported the apimanager configuration to new environment using the
tool, accessing the public API URL gives below error. It tries to check the
existence of API in the Elasticsearch. But the import/export tool never
imports anything to ES index.

Does it mean we have to explicitly migrate the existing ES index to new ES
server ?

io.apiman.gateway.engine.beans.exceptions.ApiNotFoundException: API not
found.
        at
io.apiman.gateway.engine.impl.ApiRequestExecutorImpl.lambda$execute$5(ApiRequestExecutorImpl.java:340)
        at
io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:123)
        at
io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:112)
        at
io.apiman.gateway.engine.es.CachingESRegistry.getApi(CachingESRegistry.java:117)


On Tue, Sep 18, 2018 at 12:38 PM Balu S <sbalu27 at gmail.com> wrote:

> Hi Eric, Marc,
>
> I have used this export/import option in Apiman to migrate data from 1.3
> to 1.5.1 version.The tools works fine and I can see the apis, policies and
> client apps, users are created in migrated environment.
>
> However if I notice, there are some config information stored in
> Elasticsearch under the index apiman_gateway. There are like 21 records for
> this index in Kibana. These data seems to resemble the client and api
> information.
>
> What are these data ? Is the exported "api manager"data different from
> "apiman gateway" data ? If so why are these not migrated using
> export/import utility ?
>
> Thanks for reading my post.
>
> Best regards
> Balu.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180921/e7e64a77/attachment.html