Hi APIM Team,
We observed data under repository/data grows continiously, What is the
reason for this ? Is there any way to prevent this ? I saw documentation
[1] related to data purging, Not sure we can use this to resolve this issue
?
[1]
Hi,
Is it possible to cluster two standalone APIM instances?
LB | -- APIM Standalone 1 --> DB
|--- APIM Standalone 2
If so, how do I sync tokens between the two instances?
Thanks,
Javier
If you wish to unsubscribe from receiving commercial electronic messages from
TD Bank
Hi
The problem is about the user bookmarking login page that have
sessionDataKey on the URL, somedays after that session got invalid and the
bookmark always got invalid session until user click to redirect for
correct page.
I'm try to figure ways to deal with authentication framework
Hi Clovis,
SessionDataKey is used as a state parameter between the sequence of
authentication. Within this sequence all redirections and other states are
maintained through this. Once the authentication sequence ends,
SessioiinDataKey will be removed from both Cache and DB entries. So when
you
Hi,
Is there any specific reason/requirement to use multiple proxies in your
use-case? Usually calling different services and engaging their
request/response in a single flow is done through service chaining.[1]
[1]
Hi Fazlan,
Yes. If you have indexed any table (columns), all the indexed data are
stored at repository/data.
Thanks,
Sachith
On Tue, Jul 25, 2017 at 10:14 AM, Fazlan Nazeem wrote:
> Hi Sachith,
>
> Yes. Global data purging is not the right choice. As an initial attempt,
> it
Do you mean API Manager or API Manager Analytics? It should be
repository/database right? Not repository/data because that directory is
empty by default. Once you've configured the databases properly, DBs inside
repository/database shouldn't ideally grow. Which DB are you specifically
seeing a
Hi Godwin,
Indexed data is stored in repository/data directory according to DAS
documentation[1]. If you enable data purging, indexed data should also be
cleared for those purged data. Can you try it out?
[1] https://docs.wso2.com/display/DAS301/Storing+Index+Data
On Tue, Jul 25, 2017 at 1:30
Hi Godwin,
DAS stores index data inside the repository/data folder.
There are two causes of having a large data folder.
1. Lucene stores it's index related structures there which takes a quite a
lot of space. But the size of that is limited and it would not grow.
It would stop at a particular
Hi Javier,
According to my understanding you need to cluster two API manager instances
as All-in-One instance. That means all API Manager components - Publisher,
Store, Gateway, Key Manager and Traffic Manager are deployed as one
instance.
There are two ways to achieve this.
1.
*Active/passive
Hi Sachith,
Yes. Global data purging is not the right choice. As an initial attempt, it
is better to figure out which tables are growing in a high frequency and
enable purging for them by setting a suitable time interval.
@Sachith, Does DAS store indexes in this directory irrespective of the
Hi all,
I have another question on synapse.
What is the best way to get an String representation of an OMElement? I
used the OMElement.toString() method but the documentation says about this
method:
"This is a convenience method only. This will basically serialize the given
OMElement to a
Hi dev,
I have flow: proxyA invoke proxyB and proxyB invoke backend. In this
scenario I have timeout on proxyA. When I invoke proxyB I received a
response.
Is it a problem with invoke proxy by proxy in EI 6.1.1?
--
View this message in context:
Hi all,
I have a question regarding synapse for which I could not get help from
stackoverflow[1]
I would like to check the message size of a SoapEnvelope of
org.apache.synapse.MessageContext to see if it exceeds a certain maximum
size. Currently it is done the following manner:
if
Hi,
The recommended way is to call a sequences[1] if you want to do some logic
in the mediation but invoking proxy in another proxy is not wrong. Please
share your proxy service so that it can be reproduced.
[1] https://docs.wso2.com/display/EI611/Mediation+Sequences
Regards,
Riyafa
On Mon,
Hi Melodias,
There is no problem with invoke proxy by proxy when first proxy has timeout
duration.
For all the endpoints which does not have a timeout, global timeout which
is located in synapse.properties "synapse.global_timeout_interval" is
considered. The default value is set to 120s.
Thanks
Hi all,
I tried to send the parameters in the body instead of passing them as URL
parameters from the authenticator to the external web app. It redirects to
the URL https://localhost:9443/samlsso. According to [1], sending the
parameters via the payload is supported in IS 5.3.0. I'm also using IS
17 matches
Mail list logo