6:53 a.m.
Great!
Now to throw a little wrench in the works. :)
We just released 1.0.3.Final and there is a slight change to the schema.
There is a new table and a new row to an existing table. As we don't
have any DB migration strategy (yet) you'll need to either let hibernate
upgrade your schema or create your own migration DDL.
To help with the latter, here are the DDL changes between 1.0.2 and 1.0.3:
https://gist.github.com/EricWittmann/c62456b5ff2424cd441b
And sadly, the 1.0.3 release was released with a bug in the mysql and
postgres schemas - they are missing the new 'definitionType' column in
the 'service_versions' table. As a result, I am filled with self loathing!
-Eric
PS: the missing column problem is fixed of course - latest schemas for
1.0.x can be found here:
https://github.com/apiman/apiman/tree/1.0.x/distro/wildfly8/src/main/reso...
On 2/18/2015 12:23 AM, Anton Hughes wrote:
Thanks Eric
This is perfect. I followed your instructions and all is good!
Thanks again
On Sat, Feb 14, 2015 at 4:22 PM, Eric Wittmann <eric.wittmann(a)redhat.com
<mailto:eric.wittmann@redhat.com>> wrote:
We really should have the data available in a DML of some kind,
perhaps. However, that's not available currently, so your best bet
is to configure everything manually via the UI.
That sounds hard but it really isn't!
1. Roles - create whatever roles you think you'll need. We
recommend *at least* a role equivalent to Organization Owner which
grants all permissions and is set to auto-grant:true.
2. Gateway - create a gateway with the following settings:
Name: Gateway
Description: Something sensible. :)
Configuration Endpoint: http://localhost:8080/apiman-__gateway-api/
<http://localhost:8080/apiman-gateway-api/>
Username: apimanager
Password: apiman123!
(Use the Test Gateway button to make sure the settings work!)
Note: better to set the configuration endpoint to the hostname of
the server, rather than localhost, if possible.
3. Policy Definitions - these can all be imported in a single shot.
Simply click import policy and then copy/paste the contents of
"all-policyDefs.json" into the big text area. That file can be
found in the distro, or you can use what's here:
https://raw.githubusercontent.__com/apiman/apiman/master/__distro/data/sr...
<https://raw.githubusercontent.com/apiman/apiman/master/distro/data/src/ma...
4. Profit!
-Eric
PS: we have a little java unit test that does all this, but it's
honestly easier to just use the UI to configure everything than
tweak the unit test settings to do it automatically.
PPS: once you have everything configured manually, maybe do a dump
of the postgresql db to make it easier to do again if necessary...
On 2/13/2015 8:51 PM, Anton Hughes wrote:
Hi all
This is following on from a previous thread related to migrating
from h2
to postgres.
Thanks to Ruben who answered my previous question, related to roles.
I now see that there is a lot of setup to do, such as setting up:
* gateway
* plugins
* policy definitions.
Does anyone know of a simply way to migrate data from h2 to
postgres?
Or is there away to populate postgres with the above, default,
values/settings?
Thanks and regards
Anton
*
*
*
**
*
_________________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
https://lists.jboss.org/__mailman/listinfo/apiman-user
<https://lists.jboss.org/mailman/listinfo/apiman-user>
--
*
**
*
*
Anton Hughes
Co-founder
ah(a)magick.nu <mailto:ah@magick.nu>
www.magick.nu <http://www.magick.nu>
*
*
**
*