Enterprise Integration for Beginners

This is the way of setting permissions for a role using a “carbon admin service”. Basically, this is an http post request. The endpoint is :  https://localhost:9445/services/UserAdmin.UserAdminHttpsSoap11Endpoint Replace localhost and port according management console information That should be like <esb host name>:<management console https port> Request Payload : <soapenv:Envelope xmlns:soapenv=” http://schemas.xmlsoap.org/soap/envelope/ ” xmlns:xsd=” http://org.apache.axis2/xsd “>    <soapenv:Header/>    <soapenv:Body>       <xsd:setRoleUIPermission>          <!–Optional:–>          <xsd:roleName>cg_publisher</xsd:roleName>          <!–Zero or more repetitions:–>          <xsd:rawResources>/perm...

WSO2 Carbon based products require some databases to be created for operation. Every WSO2 product comes with a folder named dbscripts (CARBON_HOME/dbscripts) and that folder contains database scripts for different types of databases. These scripts creates 3 set of tables by default. 1) Registry tables -These are related to registry artifacts of the WSO2 product.  2) User management tables – These tables are related to user management of the server. All the user permissions and roles related information will be saved in these tables. By default these are created in internal H2 database. ( We can create a separate database schema for this if we want) 3) User Store tables – These tables are related to creating actual users which are create in the server. These tables will not be used if we have pointed to external LDAP user store. From the above 3 set of tables, we will only need to focus on user management tables since we have created other tables in external LDAP and data...