does anybody know how to define static variable in WSO2 BPS that could be accessible for all processes in current BPS installation.
I tried to define property in registry but I'm unable to read its value in process instance.
I also know that I can define variable in deploy.xml but it will be per peocess not for all preocesses.
Below is picture showing defined property in WSO2 BPS Management Console.
Can someone help me with this?
Thanks in advance.
For BPEL, you can use Property Reader Extension.
Related
Frequently, WSO2 EI server getting crashed in our local environment with registry issue and every time this issue occurred I used to change the server bundle to sort this out is there any permanent solution to fix this issue?
If possible can someone explain why this issue occurred it would help me to understand why it's occurring.
This issue can be observed if the <registryPath> is not configured in Salesforce init configs. The connector might add a corrupted entry to the registry when invoking the service due to this missing config. In the latest versions of the Salesforce Connectors, this value has been set by default, hence you do not need to provide them separately.
I am working on stream processor 4.3.0 and I need to access Siddhi user guide for checking on the source types and syntax.
For some reason, this site is not reachable for MQTT and RabbitMQ.
https://wso2-extensions.github.io/siddhi-io-mqtt/
Can someone please update if the site location is changed?
Thanks
Siddhi documentations are moved to siddhi-io organisation, Please find the link, https://siddhi-io.github.io/siddhi-io-mqtt/api/2.0.0/
I have installed the basic jUDDI Server in my machine. I am able to Register the Service and able to read my Service info as a new user. I want to restrict the users who wants to look up my services. I want only my clients to access these information. I want to authenticate them so only my clients can view the business, service, tModel, Binding Template information. How can I achieve this? Can any body help me get through this?
Try turning on the setting the requires authentication for the inquiry API. You can find it in the juddiv3.xml config file for the server. Here's the xpath to get you there.
config/juddi/auth/Inquiry=true
Future readers, the documentation is located here for the current release (as of this time of this post)
https://juddi.apache.org/docs/3.3/juddi-guide/html/ch04.html#_administering_users_and_access_control
but the website https://juddi.apache.org/docs.html will get you to whatever is current. The docs (that website) is also available as part of the distribution and (i think) maven artifacts
The WSO2IS sample app instructions are less than accurate and there are some key details to the instructions are missing. Does anyone have a complete set of instructions that will actually produce a working example?
Also, it seems like localhost is coded everywhere, some guidance on how to add and update the service provider and identity provider that are on different hosts is important.
also, is the patch or service pack needed for this to run correctly? That info is not in the documentation or blogs I've been reading from WSO2
I've written a post on configuring the sample for a tenant scenario1. You should be able to configure using this. Change the hostname of SAML.IdPUrl in WEB-INF/classes/travelocity.property to that of IS. Change Assertion Consumer URL at SP registration and on WEB-INF/classes/travelocity.property to that of SP(travelocit app).
1 - how-to-configure-identity-server-sso
I'm looking at WSO2 ESB samples http://docs.wso2.org/wiki/display/ESB460/ESB+Samples+Setup
It tells me to use "./wso2esb-samples.sh -sn " to start ESB with different configurations. But I couldn't find wso2esb-samples.sh anywhere... How should I start ESB with different configuration?
And a side question, if I want to start ESB with multiple configrations, how should it be configured?
Thanks in advance!
It is located inside <ESB_HOME>/bin directory.
Samples are given to provide information regarding the common use-cases and to provide the experience the different features of the WSO2 ESB. Yes, you can configure the ESB with different configuration depend on your requirement, for that you can follow our ESB doc which gives all the information that you required...
Thanks,
Mohan