WSO2 bps 3.0.0 how install DSS feature - wso2

How can I install DSS feature to wso2 bps 3.0.0?
I try with Feature Management using http://dist.wso2.org/p2/carbon/releases/4.0.1/
I get this error :
Caused by: java.lang.Exception: HttpSession is null
at org.wso2.carbon.feature.mgt.services.prov.utils.ProvWSUtils.getResolutionResult(ProvWSUtils.java:338)
at org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminService.performProvisioningAction(ProvisioningAdminService.java:271)
... 11 more
[2012-10-06 00:43:26,584] ERROR {org.wso2.carbon.feature.mgt.ui.ProvisioningAdminClient} - Error occured while performing provisioning action
org.apache.axis2.AxisFault: Error occured while performing provisioning action
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at org.wso2.carbon.feature.mgt.stub.ProvisioningAdminServiceStub$3.onFault(ProvisioningAdminServiceStub.java:991)
Could someone please provide more information on how this could be done?

BPS 3.0.0 and DSS 3.0.0 is not yet released. It will be released in the next few days.

Related

Configuring Analytics with APIM 4.0.0 not working

Configuring Analytics with APIM 4.0.0 not working.also https://analytics-event-auth.choreo.dev/auth/v is not reachable
ERROR - EventHubClient Recoverable error occurred when creating Eventhub Client. Retry attempts will be made in 5 min. Reason :Exception class feign.FeignException$NotFound occurred.

WSO2 Api Manager 3.0 Data Mapper does not work

I have installed wso2 Api Manager 3.0 on my windows by downloading the binaries.
I wonder if the datamapper does work in the v3.0 of the Api Manager.
it does not work in my case.
I am using OOTB sequences, but unfortunately unable to actually save it:
The logs are saying that the XML sequence are not found for the datamapper, regarding the apache-synapse configuration.
Steps to reproduce the issue:
1.)Downlaod AM3.0 Binaries and install in windows machine
2.)Open publisher and create a dummy api and in request mediator select the json_to_xml or any ootb sequences. and click on save button.
SAME FLOW WORK PERFECTLY FINE IN 2.6
Please find the errror log file attached.
Please find the server logs:
org.wso2.carbon.apimgt.api.APIManagementException: Issue is in accessing the Registry[2019-11-18 17:41:43,883] ERROR - APIUtil Issue is in accessing the Registry
[2019-11-18 17:41:43,900] ERROR - APIMappingUtil Error occurred while getting the uuid of the mediation sequence
org.wso2.carbon.apimgt.api.APIManagementException: Issue is in accessing the Registry
at org.wso2.carbon.apimgt.impl.utils.APIUtil.getMediationPolicyAttributes_aroundBody322(APIUtil.java:5438) ~[org.wso2.carbon.apimgt.impl_6.5.349.jar:?]
at org.wso2.carbon.apimgt.impl.utils.APIUtil.getMediationPolicyAttributes(APIUtil.java:5373) ~[org.wso2.carbon.apimgt.impl_6.5.349.jar:?]
at
Caused by: org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException: Resource does not exist at path /_system/governance/apimgt/customsequences\in
at org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:449) ~[org.wso2.carbon.registry.core_4.5.1.jar:?]
at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2446) ~[org.wso2.carbon.registry.core_4.5.1.jar:?]

Configuring both WSO2 IS and ESB in Linux box and facing errors while starting IS server

Here is a snippet of the exception:
Caused by: org.wso2.carbon.user.core.UserStoreException: Database Error - Database may be already in use: "Locked by another process".
I am trying an example given in this url:
https://docs.wso2.com/display/IS500/2-legged+OAuth+for+Securing+a+RESTful+Service
steps:
copied both wso2 esb and wso2 is to linux box
started wso2 esb using ./wso2Server.sh --start. can access the management console.
trying to start wso2 is using ./wso2server.sh from IS_HOME/bin..And received this error.
Note: Still I can bring up the IS management console.

Configuring WSO2 API Manager to use the WSO2 BAM Server

Using WSO2 API Manager 1.3 and WSO2 BAM 2.0.
I followed the instructions found in the README.txt in /statistics.
I am getting the following error when starting API Manager:
TID: [0] [AM] [2013-05-02 11:42:44,239] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Any suggestions on where to start looking for the issue?
It looks like you have not properly configured WSO2 API Manager 1.3 to work with WSO2 BAM.
For proper configuration follow the official docs[1]
This issue might also occur When you set an offset to BAM by 1 as described in the README.txt, as it needs its Cassandra DB configurations to be changed for the offset by 1 at BAM_HOME/repository/conf/etc/cassandra-component.xml. Therefore follow the like provided[1] where we change the API Manager's offset.
Suho
[1]http://docs.wso2.org/wiki/display/AM130/Monitoring+and+Statistics

Getting error when running WSO2 API Manager with WSO2 BAM Server

I got the following error when runnning WSO2 API Manager 1.3.1 to use the WSO2 BAM Server 2.0.1.
TID: [0] [AM] [2013-05-02 18:58:40,609] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Both API Manager and BAM are running on the same machine and I changed offset to 1 in /home/jtao/api/wso2bam-2.0.1/repository/conf/carbon.xml based on Monetization of API Usage.
I also checked that BAM_HOME/repository/conf/etc/cassandra-component.xml doesn't exist in BAM 2.0.1. as someone suggested in the answer of another question "Configuring WSO2 API Manager to use the WSO2 BAM Server"
Any ideas?
I ran the same scenario described in guide and it works without any error. May be your have missed a part in the configuration guide? Make sure BAM_HOME is set correctly and BAM server is started before the AM server.
The following guide too can be used to integrate AM 1.3.1 with BAM 2.0.1
http://docs.wso2.org/wiki/display/AM131/Monitoring+and+Statistics
Ishara