If gateway server is installed in one server and api manager installed in another server and I have configured DAS in api manager server. Will my DAS server can collect statistics data from api manager server?
If you are using gateway manager or gateway worker profile then you need to enable below OSGI bundles in bundles.info for that profile
org.wso2.carbon.bam.service.data.publisher.stub,4.6.0,../plugins/org.wso2.carbon.bam.service.data.publisher.stub_4.6.0.jar,4,true
org.wso2.carbon.bam.service.data.publisher.ui,4.6.0,../plugins/org.wso2.carbon.bam.service.data.publisher.ui_4.6.0.jar,4,true
org.wso2.carbon.statistics,4.4.8,../plugins/org.wso2.carbon.statistics_4.4.8.jar,4,true
org.wso2.carbon.statistics.stub,4.4.8,../plugins/org.wso2.carbon.statistics.stub_4.4.8.jar,4,true
org.wso2.carbon.statistics.ui,4.4.8,../plugins/org.wso2.carbon.statistics.ui_4.4.8.jar,4,true
Related
I want to integrate a payment service in my web application but the service provider needs a PCI Certificate for my web application as to see the current situation I'm thinking to move my server on AWS Amplify since AWS is a PCI DSS Compliant so if I host my web app do I get a separate PCI Certificate from AWS which I can show to the payment service provider for the payment integration.
I'm confused if I used AWS Amplify do AWS provide me a PCI Certificate for my web application. Please elaborate me regarding this.
Thanks
I have configured WAF load balancer for three api gateway server and now I also have two analytics server, how should access to analytics dashborad? should I configured another load balancer for access to analytics dashboard?
could you please guide me?
I'm using 2 instances of WSO2 API Manager 2.1.0 within the same node. (one instance as a gateway which is exposed to DMZ)
I tried to configure the WSO2 Analytics Server and came up with the following concern.
Since the gateway is already up and running with an offset of 1, how should I be setting the offset in the Analytics Server in order to get it to work? In the documentation, I noticed this: "By default, WSO2 API Manager has a port offset of 0 (no port offset) and WSO2 API Manager Analytics has an offset of 1. Therefore, this guide assumes that you do not have any other carbon servers running on the same machine with port offsets of 0 or 1." If so how should I proceed with configuring the Analytics Server?
Should I configure 2 Analytics Servers for both instances?
Any guidance for these concerns is highly appreciated.
Thanks in advance.
Configure a different port offset for the analytics server. You can configure the offset in <ANALYTICS_HOME>/repository/conf/carbon.xml. Set the offset as <Offset>2</Offset>. By configuring this, Your analytics server can be up in a different port (APIM_PORT+2).
Only one instance of Analytics is enough. Point all your APIM instances to the analytics server you configured.
I am trying to add DataPower 7.7 into API Management 2018.1.
I need to configure API Connect Gateway Service in DataPower (new APIC 2018.1 doesn't work with XML Management Service).
After configuration I got an error:
8:07:19 mgmt notice 959 0x00350015 apic-gw-service (default):
Operational state down
8:07:19 apic-gw-service error 959 0x88e00001 apic-gw-service
(default): Unexpected queue error: Domain check failed! Please ensure that
the 'default' domain exists and is enabled. Also, please verify that the API
Gateway Service is configured with the correct domain and SOMA credentials.
8:07:19 apic-gw-service error 959 0x88e000a0 apic-gw-service
(default): Failed to initialize gateway environment: datapower
DP version is 7.7.
Please suggest, if you have any information or manuals.
Note: Domain exists, main services are enabled
It's hard to tell what exactly the problem is based on the log messages shown above.
Update to original answer:
See also the documentation that is now available in the IBM API Connect Knowledge Center: https://www.ibm.com/support/knowledgecenter/SSMNED_2018/com.ibm.apic.install.doc/tapic_install_datapower_gateway.html
However, here are the basic steps for configuring a DataPower gateway to work with API Connect 2018.x.
You will need to ensure:
DataPower is running DP 7.7.0.0 or higher.
You have the AppOpt license installed. (Use the “show license” command in the DataPower CLI to confirm.)
You have a shared certificate and a private key for securing the
communication between the API Connect management server and the
gateway.
On DataPower, you need to:
Create an application domain. All of the subsequent configuration should be done in the application domain.
Enable statistics
Upload your private key and shared certificate to the cert:// directory in the application domain.
Create a crypto key object, a crypto certificate and a crypto identification credentials object using your key and certificate.
Create an SSL client profile and an SSL server profile that reference the crypto identification credential object.
Configure a gateway-peering object.
Configure and enable the API Connect Gateway Service in the application domain.
At that point, you should be able to configure the gateway in the API Connect cloud manager.
Here are the DataPower CLI commands to create a basic configuration. In the configuration below, IP address 1.1.1.1 represents a local IP address on your DataPower appliance. Traffic from the API Connect management server to the gateway will be sent to port 3000. API requests will go to port 9443 (but you can change it to the more standard port, 443, if you prefer.)
For a production environment, you will want to build on this configuration to ensure you are running with at least 3 gateways in the peer group, but this will get you started.
Create the application domain called apiconnect
top; configure terminal;
domain apiconnect; visible default; exit;
write mem
Use the Web GUI to upload your private key and shared certificate to the cert:// folder in the apiconnect domain
Then run these commands to create the configuration in the apiconnect domain
switch apiconnect
statistics
crypto
key gw_to_apic cert:///your-privkey.cer
certificate gw_to_apic cert:///your-sscert.cer
idcred gw_to_apic gw_to_apic gw_to_apic
ssl-client gwd_to_mgmt
idcred gw_to_apic
no validate-server-cert
exit
ssl-server gwd_to_mgmt
idcred gw_to_apic
no request-client-auth
validate-client-cert off
exit
exit
gateway-peering apic
admin-state enabled
local-address 1.1.1.1
local-port 15379
monitor-port 25379
priority 100
enable-ssl off
enable-peer-group off
persistence local
exit
apic-gw-service
admin-state enabled
local-address 0.0.0.0
local-port 3000
api-gw-address 0.0.0.0
api-gw-port 9443
v5-compatibility-mode on
gateway-peering apic
ssl-server gwd_to_mgmt
ssl-client gwd_to_mgmt
exit
write mem
The problem you are seeing is an issue with creating your api connect service in the default domain. To work around just put your Api Gateway Service in a domain other than default.
I'm new to WSO2 products and the company I worked for asked me to evaluate WSO2 Enterprise Service Bus (ESB). Aside from this they also wanted to evaluate the WSO2 Identity Server (IS) and WSO2 API Manager (APIM). So we created a test system installing ESB as the base product. After researching most of the references in the web states that you can install other WSO2 products inside an existing one by installing it's feature. So we decided that approach and after a few issues we have successfully installed APIM and IS inside a running ESB. However while accessing the APIM Publisher by using the url https://:9443/publisher we got an error
HTTP Status 405 - HTTP method GET is not supported by this URL
type Status report
message HTTP method GET is not supported by this URL
description The specified HTTP method is not allowed for the requested resource.
Apache Tomcat/7.0.34
Any idea what happened as we have not seen any errors on the logs? Is it possible if I just install on a separate instance the WSO2 APIM but assigning it to a different port so as to avoid conflict with the ESB?
Thanks for the help.
Is it possible if I just install on a separate instance the WSO2 APIM
but assigning it to a different port so as to avoid conflict with the
ESB?
Port offset allows you to run multiple WSO2 products, multiple instances of a WSO2 product, or multiple WSO2 product clusters on the same server or virtual machine (VM). Port offset defines the number by which all ports defined in the runtime such as the HTTP/S ports will be offset.
For example, if the default HTTP port is 9763 and the portOffset is 1, the effective HTTP port will be 9764. Therefore, for each additional WSO2 product instance, set the port offset to a unique value (the default is 0) so that they can all run on the same server without any port conflicts.
Port offset can be passed to the server during startup. The following command starts the server with the default port incremented by 3.
./wso2server.sh -DportOffset=3
Alternatively, you can set it in the Ports section of <PRODUCT_HOME>/repository/conf/carbon.xml as follows:
<Offset>3</Offset>
Hi You dont need to install API manager features in the ESB. You can take a API Manager instance instead which has a lightweight ESB running inside. you can access this from the management console on the API Manager