Mapping application module to roles/profile pattern

[lupin...@gmail.com]

Hi,

I'm lost on how to map my module usage to roles and profiles, particular case is with IBM Websphere but I guess the use case goes with other application server module.

So in Websphere  https://forge.puppetlabs.com/joshbeard/websphere one can have;
 * multiple instances running inside an OS host e,g /opt/instance0, instance1
 * within an instance you can have multiple Websphere  application profiles(runtime) and one deployment manager profile.


What would be the sane approach of mapping it to roles/profile pattern?

I can have a role::A  which will then only have a multiple websphere application profiles
 or
I can have a role::A which will then have a deployment manager profiles + multiple application profiles.

In the profiles module what should be included?

profiles::websphere::profiles
  include websphere
  ::websphere::profiles

Thanks,
Lupin