We are using JBOSS EAP 6.4 with WMQ adapter. We have a MDB whose activation config properties are configured inside "ejb-jar.xml". Application is already deployed into the production and we need to override/add new activation config property. We can not afford to modify ejb-jar.xml and create new release archive.
Is it possible to override existing "activation-config-property" or add new "activation-config-property" using standalone deployment descriptor?
I referred to similar SO threads (mentioned below). But nothing was helpful:
Change Activation-Config-Property on deployment via JBoss CLI
Changing Activation Config of Topic reading MDB at deploy time
MDB set ActivationConfig dynamically
Please let me know if you have any idea on to override these activation config properties using standalone descriptor or using JBOSS CLI.
Thanks,
A deployment overlay should help in your situation:
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/6.4/html/administration_and_configuration_guide/deployment_descriptor_overrides
Related
I have been trying to integrate IBM WebSphere MQ with WildFly server, as part of a application-server redeployment POC.
Have managed to deploy and added the resource adapter (wmq.jmsra.rar).
Also, managed to set-up the jmsQueueConnectionFactory via Connection Definitions, and jmsQueue via Admin Objects.
However, can't seem to find a configuration which would allow for setting of jmsActivationSpec. Greatly appreciate some help!
I just want to double-check what the exact steps are for updating the MQ Resource Adapter in JBoss.
I can find a lot of guides on how to deploy it and configure it, but none on updating it.
I have got JBoss 6.3 and MQ RA 7.5.0.5 (need to update to RA 7.5.0.9). Is it just a matter of stopping the application server, removing wmq.jmsra.rar from the deployment directory, copying the new wmq.jmsra.rar version in there and starting up JBoss?
Moving from 7.5.0.5 to 7.5.0.9 is a very small update so I wouldn't expect there would be any configuration updates required. The process you outlined (i.e. stop JBoss, update rar, start JBoss) should be perfectly fine.
we are migrating one application from JBoss AS 6 to 7.
This new instance is useing the standalone-ha profile. On the previous version, we used a custom Infinispan loader which stored the cache entries into our custom database.
Now, on JBoss 7.1, when trying to change this configuration using the visual administration console, it don't work. The value that we type on the tab "Store Class Impl" on "Replicated caches" is not being stored on the profile configuration as it should be. So, here is my question: is it possible to change this configuration using xml? How can I configure this custom loader for our replicated caches? Does anyone here ever experience this kind of dificulty?
Unfortunately I can't provide you any valuable information about JBoss admin console.
Anyway, I would suggest you to set up cache stores/loaders for your Infinispan caches declaratively (using configuration xml file) or programmatically (using fluent API builder just in code).
Here you can find more details about stores/loaders and some example configurations: https://docs.jboss.org/author/display/ISPN/Cache+Loaders+and+Stores
And also take into account that in the recent Infinispan version (5.2) there is no possibility to change cache configuration "on fly". You need to restart your service with new configuration in case of any wanted change.
(What do you exactly mean by custom Infinispan loader?)
Is there a deployment folder where a war can be placed in the master node so that it gets deployed to all the slave nodes in a domain managed setup in JBoss AS7?
I know that we can use the JBoss CLI to deploy to a server group which places the artifact in the JBOSS_HOME/domain/data//content directory.
However I would like to find out if there is a way that it can be placed in a deployments folder under the domain of the master node (e.g. JBOSS_HOME/domain/deployments) that is similar to the one available in the standalone mode (i.e. JBOSS_HOME/standalone/deployments) so that the deployment scanner picks it up and makes it available to the slave nodes in the domain without the explicit deploy command via CLI.
To summarize the comments above: There is no deployment directory in domain mode.
You can use the CLI
the web console
the maven plugin
or create your own deployment manager.
I wrote a, now old, blog post on how to do this on a standalone server, but it could be slightly changed to use on a domain server. Have a look at how it's done with the jboss-as-maven-plugin for an example.
We were using JDev to develop our applications and deploy them to OC4J and OAS.
we used to use JDev to create the data-source configuration for us both on dev and on deployment. (on dev using the wizard that come with jdev to connect to data-source.. and on deployment hence we don't need to do any Data-source configurations on the app server manually)
But, when we moved to eclipse, we couldn't no longer be able to deploy the EAR file unless we create the data-source manually (either using the em or j2ee\home\config\data-sources.xml but on some deployment, we may not be able to do such thing.
So, can we add some files for example to the EAR so that we can tell OAS that we need from it to create the DS for us??
Hint (I am hearing about some thing named orion*.xml, is this related to that request??
Thanks.
You can.
You need to place the correct data-sources.xml into your EAR/META-INF and reference it from your EAR/META-INF/orion-application.xml the same way as j2ee\home\config\data-sources.xml is referenced from j2ee\home\config\application.xml