Hi,
Subash, as I found the CAR file could be deployed via the file-system by
copying it to repository/deployment/server/carbonapps/ before starting the
ESB. Therefore I prefer the CAR file method over the G-Reg check-in tool.
Shavantha, yes I could test this approach during ESB 4.8.1 testing. If
Hi imesh
We can tryout this approach during 4.8.1 testing
Regards,shavantha
On Jan 24, 2014 6:21 PM, Imesh Gunaratne im...@wso2.com wrote:
Hi,
I found a better approach than using the G-Reg check-in tool.
We could create a CAR archive including a Registry Resources Project and
deploy the
Hi,
I found a better approach than using the G-Reg check-in tool.
We could create a CAR archive including a Registry Resources Project and
deploy the CAR file directly in the ESB.
Thanks
On Thu, Jan 23, 2014 at 5:00 PM, Imesh Gunaratne im...@wso2.com wrote:
Hi,
I was able to do the
Hi Imesh,
CAR method is also a good option. But when it comes to deployment, ideally
it should be a one time operation for an instance. Once this car in place,
it will get deployed in each server restart which I believe unnecessary for
this particular scenario. In such case checkin client makes
Hi,
As I found BAM Profiles in ESB are stored in the registry (ESB 4.8.0).
Is there a way to configure this without accessing the ESB Dashboard (if we
could export the required configuration to a file)?
I tried to use the G-Reg check-in tool but it was not successful with the
H2 database.
Hi,
I was able to do the following with G-Reg check-in tool and successfully
configure the BAM Server Profile outside the ESB Dashboard:
1. Start a fresh ESB instance.
2. Checkout _system/config path to a local folder (A1) using check in
client.
3. Create bamServerProfiles folder at A1.
4. Copy
