WSO2 enterprise integrator - datasource - wso2

do you know where is save settings about datasource from wso2 EI?
i create datasource on GUI in wso2 but I can't find record on server.
Thanks

You can find the dataservice file under,
EI-Home/repository/deployment/server/dataservices
Datasources added from Management Console will be stored in registry,
/_system/config/repository/components/org.wso2.carbon.ndatasource/

The data sources added from the Management console UI is saved to the registry under /_system/config/repository/components/org.wso2.carbon.ndatasource registry path. You can navigate to the registry path from management console UI and you can download the data source definition created from there.
registry path
If you need to add data source definitions from the file system you can create a file with format {any_name}-datasources.xml and put the data source configurations and save it under {SERVER_HOME}/conf/datasources

Related

how to resgist datamapper mediator in WSO2 ei

Now I want to use data mapper mediator in WSO2 ei console, and it requires me to select some Configuration Registry files:
but I don't know how to register these configuration, in the WSO2 EI documentation I could hardly find how to register, while I only found that I can create a ESB solution project and package that to a .car file, then deploy it.
But I don't want to do this, so I need help.
I believe what you're looking for is in this link.
Mapping Configuration: The file, which contains the script file that is used to execute the mapping. You need to create a mapping
configuration file using the Dev Studio-based Tooling plugin, and
store it either in the Configuration Registry or Governance Registry,
to select and upload it from here.
Let me know if it worked or need more help.

wso2 custom synapse file is not copied over to newly created tenant

I have a multi-tenant wso2 API manager 1.10.0. I am developing a class mediator with business logic, which will be part of out sequence. I have put this new sequence file (xxx.xml) into (carbon-home)/repository/deployment/server/synapse-config/default/sequences directory, and restart the wso2 server. But when I create a new tenant, all other xml files in that directory get copied into the newly created tenant directory and SVN repository, but not my file.
Is there anything I need to do to tell wso2 server about my new sequence file so that it can pick it up?
Thanks for the help!
When you create a new tenant, it will not create any custom files from super tenant. It will only create the default files that available on repository/deployment/server of a fresh pack.
Therefore you have to manually copy your custom file or create that artifact again using the management console (in tenant)

WSO2 Custom Handlers in a Cluster

In a cluster, where does WSO2 APIM store the configuration files that, in a non-clustered deployment are kept under:
<wso2_home>/repository/deployment/server/synapse-configs/default/api
I published a Ticket API through Publisher in a clustered deployment of WSO2 but haven't found the corresponding 'admin--TicketAPI_v1.0.xml' file anywhere. The clustering guide creates several databases. Would this xml file be stored in any of the WSO2 databases? If so, where? What I need to do is to add Custom Handlers to my API by adding to the "handlers" section of the 'admin--TicketAPI_v1.0.xml' file, as explained in the Writing Custom Handlers doc. How is this accomplished in a clustered deployment?
You should be able to find admin--TicketAPI_v1.0.xml file in your gateway node
/repository/deployment/server/synapse-configs/default/api
Your admin--TicketAPI_v1.0.xml file should be there in one of the gateway worker nodes.
However, It is not recommended to update the API source code via the source view UI or file system when engaging a custom handler to selected APIs, because the customizations get overridden by the publisher updates.
So the recommended way is to add the custom handler that you wrote to the velocity_template.xml found in /repository/resources/api_templates/velocity_template.xml

WSO2 ESB How to upload app config xml files

I need to work around a weird behaviour of WSO2 ESB. Whenever the ESB is started, all carbon files are redeployed. This means to reset all changes made in files after last deploy(restart), such us, configuration xml files (endpoints, custom config files...) .
So I guess the only way to avoid modifing this configuration files during the start up is to take them out from the carbon file. Thus, I would upload app files as carbon app, and app config files (EP, custom config files...) using an alternative way.
So, in this situation, how could I upload these config files in and easy and automatic way?
Regards
I presume you are using a CApp (Carbon Application) to deploy the esb artifacts like endpoints. The number rule for this procedure is that you need to do all the modifications you need to do via the WSO2 Developer Studio, build a CApp, and re-deploy it in WSO2 ESB. You should try to avoid using management console to perform esb artifact (proxy services, endpoints, sequences, templates etc.) modifications. You can of course use the management console for other administrative tasks like configuring data-sources, BAM mediation data publishing etc.
If you are using the Management console to modify artifacts, then you can do that too, but avoid using CApps as the method of deploying esb artifacts. You should probably copy all the config xml files to relevant folders at $ESB_HOME/repository/deployment/server/synapse-configs/default/. And then go ahead with your modifications via mgt console.

Is there a way to clone the deployed data service on the WSO2 DSS

I created a data web service on the WSO2 Data Services server, now I would like to use it as a template so I can create more services out of it.
Is there a way to copy/paste the service XML to a new one?
I would like to skip the wizard mode creation.
Go to service Dashboard and there you have "edit data service (xml edit)" option available. That can be reused to create similar services. create a .dbs file out of that xml content and deploy through upload data service option in the management console (Change the data service's name). Following link would be useful.
[1] http://docs.wso2.org/wiki/display/DSS301/Work-In-Progress+Service