Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MessageBus in configuration manifest export #163

Open
earthlingdave opened this issue Mar 5, 2019 · 1 comment
Open

MessageBus in configuration manifest export #163

earthlingdave opened this issue Mar 5, 2019 · 1 comment

Comments

@earthlingdave
Copy link

Hello,

we exported our complete (wdr.tools.exportConfigurationManifestToFile(getid('/ServerCluster:id:/'), 'clusters.wdrc', wdr.export_sets.all)) ServerCluster successfully, but we do not see the messageBus config. Just the reference (propertiesSets) of the message bus for our queues.

  • J2CResourceAdapter
    • j2cActivationSpec (QueueName+ "AS")
    • j2cAdminObjects (QueueName)
  • J2CConnectionFactory (QueueName + "ConnectionFactory")

Can we run into an issue when the messageBus is not existing during the import? (create this cluster)
Is it possible to export the messageBus?

Thanks in advance!

David

@mplonka
Copy link
Member

mplonka commented Apr 12, 2019

Hello David,

SIB objects shouldn't be very different from other configuration elements, therefore you should be able to export/import them as long as you have the right export-set for them. One thing that makes them a bit more special is that they use internal UIDs, which need to be aligned with their UIDs in the database or file store. Due to historical reasons (I never dealt too much with SIBuses) WDR does not provide SIB-specific export-set. Should you have one and should you be interested in sharing it - feel free to open a PR.

Regards,
Marcin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants