How to Set MQGet CodedCharSetID in Apache Camel - character-encoding

currently I am working with Apache Camel and IBM Websphere MQ. In my project, I would like to write xml message into IBM WMQ and to do so I need to change the MQGet CodedCharSetID from 1208 into 819.
Anyone has an idea about how to do so in apache camel?
For your information:
I have tried to use the convertbodyto tag, but it did not worked.
I have also tried to add CCSID property in WMQ Connection Factory Bean, and it also did not worked.
Your help is so much appreciated. Thanks in advance.

Try setting the destination name as queue:///FOO.BAR?CCSID=819 instead of simply FOO.BAR
If that does not work out, there is a workaround to set the option on Camel JMS docs.

Related

WildFly datasource connection-properties

I'm using WildFly 21.0.1-Final.
My problem is that I want to set a custom connection property for the Oracle driver. I am not able to do that using jboss-cli nor admin console web interface.
The default property is:
jboss-cli error:
Web app error:
I'm getting the error. It looks like the '$' sign is a problem .... ???
Appreciate any help! Thanks in advance )
Finally escaping $ sign with the back slash did the trick. But I should admit that this approach works only with jboss-cli and not with Web Management Console.
Thanks ehsavoie for giving me the hint.

Error while creating send handler for WCF Custom Adapter in BizTalk 2016

While trying to add the host instances to the WCF Custom Adapter as a send handler I am getting the below error messages.
I tried resetting my password and restarted and that didn't work. Also, I tried to change the domain of my machine and bring it back to the original domain but I was not able to do it because of access issues.
Can someone please suggest why this error is occurring at this stage and how can I resolve it?
The above issue is resolved now. The actual problem was with the workstation/Computer name. At the time of BizTalk configuration I had only given the workstation/computer name, but instead we should give FQDN (fully qualified domain name) like workstation1.xyzcorp.net while configuring biztalk. This resolved my issue.
Thanks.

Spring Cloud Config Server - Where to set encrypt.key to enable /encrypt endpoint

I have a Spring Cloud Config app with the Spring Cloud Security dependencies. I'm trying to hit the /encrypt endpoint to encrypt a password.
According to the docs at http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html#_key_management I believe I need to set a symmetric key using "encrypt.key". But I can't figure out where to put this; all combinations I've tried result in {"description":"No key was installed for encryption service","status":"NO_KEY"} when I attempt to POST to /encrypt.
If I POST a key to /key, the /encrypt works perfectly, so I'm pretty sure that everything else is setup correctly. It also works fine using the environment variable ENCRYPT_KEY, or by using a system property encrypt.key. I just can't figure out where to place the encrypt.key within a configuration file. Is there a sample on this?
Thanks #pVilaca, this is indeed what the documentation says, but setting the key in application.properties or application.yml won't work.
Through experimentation I've found that the only place you can set the encrypt.key property is an ENCRYPT_KEY environment variable, a system property, bootstrap.properties, bootstrap.yml, or calling the /key endpoint.
Not sure why application.properties or application.yml don't work in this case. Setting this key must have more of an impact on the startup process than it would appear.
Setting Spring Cloud Version to 'Brixton.SR5' worked for me. For some reason, setting 'encrypt.key' in either application.properties/yml or bootstrap.properties/yml in later Spring Cloud Version does not work anymore.
check properties tag of pom.xml file. If you are using version 2 or 3 of Dalston, change it to:
<spring-cloud.version>Dalston.SR1</spring-cloud.version>
and it should be working fine. In my case i was using version 3 and changing it to version 1 resolved the issue for me.
Reference:
https://github.com/spring-cloud/spring-cloud-config/issues/767
If you're using spring cloud with spring boot, that is the method that is described on the documentation that you mentioned, you've two 'main' properties files.
bootstrap.[properties,yml]
To modify the startup behaviour you can change the location of the config server using bootstrap.properties (like application.properties but for the bootstrap phase of an application context)
application.[properties,yml]
where the "application" is injected as the "spring.config.name" in the SpringApplication (i.e. what is normally "application" in a regular Spring Boot app)
source: Spring Cloud Config Documentation
So, it should be enough to set the encrypt.keyin your application.[properties,yml] file (or the alternative name if specified)

Setting serviceURI for ClientFormsAuthenticationMembershipProvider

I'm searching a way to set the serviceURI for ClientFormsAuthenticationMembershipProvider in code behind. I wish not to have the app.config being changed. Is this possible ?
I'm accessing services from a windows service as well as from a windows program and configuration should be handled in a central place.
Thanks,
Sascha
It is possible to cast to ClientFormsAuthenticationMembershipProvider ClientFormsAuthenticationMembershipProvider just before doing the authentication. If casted you have a property ServiceUri. Set it and it's done.

Silverlight 3 with Weborb for Java

For some reason, i can not invoke java method deployed under Tomcat/Weborb application. When i run weborb console and invoke the method from there, there is no problem. However when i tried to call from Silverlight 3 client, it does not response at all. There is one possibility which is incorrect service gateway. But i have checked the server path to make sure it is correct. I also tried different approaches to invoke server call such as proxy and class interface mentioned inside weborb documentation. I'm stuck with this problem for two days already and can not progress any further. Is there any common mistake when it comes to this problem? Any help would appreciate.
Cheers,
Khoa Nguyen
I found the solution. This is because the gateway mapping is incorrect. For instance, When deploy under weborb, the client use localhost:8080/weborb.wo. However when you deploy underworb, the gateway mapping is now change to something like localhost:8080/weborb/console/weborb.wo something like that. You can see how your request mapped to by run the weborb console and look at the server status as you invoke your java methods.
Hope this help.
Cheers,
Khoa Nguyen
There is a new WebORB for Java 4.1 release available that fixes this mapping issue. In addition, the new code generator creates a complete client class library with complex types, enums, bindable model and proxy class for the remote Java service. The release is available here:http://www.themidnightcoders.com/products.html

Resources