App Connect

Has anyone used a bar file on openshift (or maybe ACEaaD) to deploy policies in stead of using the policy project type configuration resources?

I'm wondering what the added benefit of the policy project type is.

Policy project type

You need to zip an entire policy project, base64 encode it, and add it to a configuration resource

Policy bar file

Build the policy project as a bar file and reference your application to include the bar file. When working from a build pipeline this seems to be way easier to do.

Anyone have any experience with this?

I thought you'd just reference the policy project and it would be added to your bar file? Would that not work for your pipeline?

Has anyone used a bar file on openshift (or maybe ACEaaD) to deploy policies in stead of using the policy project type configuration resources?

I'm wondering what the added benefit of the policy project type is.

Policy project type

You need to zip an entire policy project, base64 encode it, and add it to a configuration resource

Policy bar file

Build the policy project as a bar file and reference your application to include the bar file. When working from a build pipeline this seems to be way easier to do.

Anyone have any experience with this?

Then you are referencing a policy project, not something you would do by default. Not me anyway.

I don't like combining stuff in one bar file, if it's a shared policy project with mq connections or something, you might not want that.

But my question stands, what is the benefit of the policyproject type?

I thought you'd just reference the policy project and it would be added to your bar file? Would that not work for your pipeline?

Has anyone used a bar file on openshift (or maybe ACEaaD) to deploy policies in stead of using the policy project type configuration resources?

I'm wondering what the added benefit of the policy project type is.

Policy project type

You need to zip an entire policy project, base64 encode it, and add it to a configuration resource

Policy bar file

Build the policy project as a bar file and reference your application to include the bar file. When working from a build pipeline this seems to be way easier to do.

Anyone have any experience with this?

One advantage is that it provides clearer decoupling of the integration logic in the BAR file from the configuration used by the integration. It enables you to keep the BAR file as a resource that you promote between environments (development -> test -> production) without modifying, and you can have the configuration separate that may be different in each environment - i.e. referencing test endpoints of credentials in lower environments and production system details for production.

Then you are referencing a policy project, not something you would do by default. Not me anyway.

I don't like combining stuff in one bar file, if it's a shared policy project with mq connections or something, you might not want that.

But my question stands, what is the benefit of the policyproject type?

I thought you'd just reference the policy project and it would be added to your bar file? Would that not work for your pipeline?

Has anyone used a bar file on openshift (or maybe ACEaaD) to deploy policies in stead of using the policy project type configuration resources?

I'm wondering what the added benefit of the policy project type is.

Policy project type

You need to zip an entire policy project, base64 encode it, and add it to a configuration resource

Policy bar file

Build the policy project as a bar file and reference your application to include the bar file. When working from a build pipeline this seems to be way easier to do.

Anyone have any experience with this?

Then you are referencing a policy project, not something you would do by default. Not me anyway.

I don't like combining stuff in one bar file, if it's a shared policy project with mq connections or something, you might not want that.

But my question stands, what is the benefit of the policyproject type?

I thought you'd just reference the policy project and it would be added to your bar file? Would that not work for your pipeline?

Has anyone used a bar file on openshift (or maybe ACEaaD) to deploy policies in stead of using the policy project type configuration resources?

I'm wondering what the added benefit of the policy project type is.

Policy project type

You need to zip an entire policy project, base64 encode it, and add it to a configuration resource

Policy bar file

Build the policy project as a bar file and reference your application to include the bar file. When working from a build pipeline this seems to be way easier to do.

Anyone have any experience with this?

Has anyone used a bar file on openshift (or maybe ACEaaD) to deploy policies in stead of using the policy project type configuration resources?

I'm wondering what the added benefit of the policy project type is.

Policy project type

You need to zip an entire policy project, base64 encode it, and add it to a configuration resource

Policy bar file

Build the policy project as a bar file and reference your application to include the bar file. When working from a build pipeline this seems to be way easier to do.

Anyone have any experience with this?