Recent Discussions
Does anyone have experience of accessing files on a windows network file share?
The file writer snap is not cooperating, it’s says it’s succeeding but doesn’t appear to do anything. Currently have an account mapped with read/write permissions, using fille:/// anything else generates an error or creates a file with a weird name on the plex. any help much appreciated. Yours, AdrianAdrianH9 years agoNew Contributor II6.6KViews0likes8CommentsSnaplex nodes running with customer signed SSL certificate - default SnapLogic SSL certificate selected and returned by server during SSL handshake
We have configured our Snaplex nodes to run with a customer signed SSL certificate. We use the FQDN in the certificate. The default SnapLogic SSL certificate is not in the JCC’s keystore (jcc.serverkeys.jks). However, when we test the server (Snaplex node) is returning the default SnapLogic SSL certificate to the client during the SSL handshake instead of returning the customer signed SSL certificate. We did some additional investigation and it appears that if the client has the Server Name Indicator (SNI) TLS extension enabled the server selects and returns the default SnapLogic SSL certificate. However, if the SNI TLS extension is disabled the server selects and returns the customer signed SSL certificate that’s in the JCC’s keystore. We tested the following: “openssl s_client -connect node.example.com:8081” does not use the SNI TLS extension (i.e. server name is not in the client hello message) and the server selects and returns the company signed SSL certificate chain. “openssl s_client -connect node.example.com:8081 -servername node.example.com” uses the SNI TLS extension (i.e. server name is in the client hello message) and the server selects and returns the default SnapLogic certificate. “./java -Djavax.net.debug=ssl SSLPoke node.example.com 8081” uses the SNI TLS extension (i.e. server name is in the client hello message) and the server selects and returns the default SnapLogic certificate. “./java -Djavax.net.debug=ssl -Djsse.enableSNIExtension=false SSLPoke node.example.com 8081” does not use the SNI TLS extension (i.e. server name is not in the client hello message) and the server selects and returns the company signed SSL certificate chain. We also tested via browser and curl - they use the SNI TLS extension by default (i.e. server name is in the client hello message) and the server selects and returns the default SnapLogic certificate. I didn’t find a way to disable the extention when using a browser or curl (we’re using version 7.27.0 of curl) Has anyone else encounter this behavior and been able to resolve it?6.2KViews0likes11CommentsUsing the power of data introspection and SnapLogic's Amazon S3 Snap to access your data!
We believe in a simple, click not code approach to integration. In this video, you can see how simple it is to access your data from amazon S3 buckets. Let me know what you think!ajain8 years agoFormer Employee5.9KViews0likes7CommentsKubernetes for snaplogic - custom metrics not working
Hi i have been following the tutorial from the Snaplogic documentation https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/2017558845/How+to+Deploy+a+Groundplex+in+Kubernetes about deploying Groundplex in Kubernetes. When i deploy the prometheus adapter and check the custom metrics api with this command (kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1 | jq . ), I am getting empty response - resources field is not populated with values. I have also attached the response from the api i am supposed to get , and the one that i am getting. Any help on why i am getting empty resources field without any values would be appreciated.Igor_Bozhinovsk4 years agoNew Contributor III5.2KViews0likes7CommentsHow can i setup logrotate for jcc_output.log?
Hi all, How can i setup logrotate for jcc_output.log ? in this moment this log is very big on all snaplogic servers ( 60 GB ) and i need to know how can i configure logrotate for these logs. Best regards, PetricaSolvedPetrica8 years agoNew Contributor II4.8KViews0likes4CommentsHow to integrate 3rd party job scheduler (e.g. Cisco Tidal) to kickoff and monitor SnapLogic pipeline execution
This document demonstrates how to integrate 3rd party job scheduler (e.g. Cisco Tidal) to kickoff and monitor snaplogic pipeline execution. Invoke: Deploy the SnapLogic integration pipeline as a trigger task Invoke the SnapLogic pipeline execution from Tidal through the URL (ground or cloud) Design the long running pipeline to be asynchronous to avoid timeout (firewall, Snaplogic control plane) Monitor: Use the SnapLogic Pipeline Monitoring API to check for execution status You can find the Snaplogic pipeline monitoring API here Case Study: A master pipeline to accept all the Tidal request and distribute accordingly (Triggered) Call different snaplogic trigger task based on the request. e.g. https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/organization_name/projects/project_name/pipeline_name Log the Tidal Job ID & SnapLogic pipeline runtime ID into Database for status check Database table to include the key fields: Tidal Job ID, SnapLogic Pipeline Runtime ID, Status Response to Tidal request to close the connection to avoid time-out A monitoring pipeline to update Tidal regarding the execution status (Scheduled) Query the Database for running pipeline Obtain the pipeline execution status using the SnapLogic pipeline runtime ID (Rest Call) e.g. https://elastic.snaplogic.com/api/1/rest/public/runtime/organization_name/ruuid? Update the Tidal regarding the execution status using Tidal Job ID Update the Database with the new status4.4KViews0likes2CommentsWhat happens during the Snaplex Upgrade
When the Snaplex is upgraded: a) JCCs will go through a rolling restart. As one JCC is being restarted, the others will continue processing the pipelines on the older version. The next JCCs will wait for max 15 minutes (configurable value at the snaplex level) for the running pipelines to finish, before they get restarted. b) FeedMasters (FM) will go through a rolling restart. One FM will be up and running as the other goes into restart mode. The running FM will queue up the messages in the inbound queue up to 10GB size. When FMs restart they will persist the messages from the queue to the disk. These will be retrieved back into the queue from disk. Once JCCs are up, FM starts sending the messages from the queue to be processed.vdandu8 years agoFormer Employee4.1KViews1like3CommentsAbout the Programs and Events category
This section contains subcategories for user groups, events, community-related program. User Groups User Groups create a place where users of the same industry can discuss solutions relevant to them or users of a particular region can discuss a meetup. Groups are hidden until you are member. User Group Community Group Higher Education higher-ed-users EMEA Users EMEAUsers Don’t see a group that matches your field or region? Contact the Community Manager (@dmiller). Events Events holds information about SnapLogic webinars and events. Programs Coming soon!dmiller8 years agoFormer Employee3.9KViews0likes4CommentsAES Decrypt Snap - Urgent help
Hello Smart folks, I am having a requirement to AES Decrypt a field(the field was encrypted with ‘AES/CTR/NoPadding’ algo with dynamic Secret key and initialization vector key by external system). Dynamic mean here is my input fields are supposed to be decrypted by different Secret key and Initialization vector in each pipe run so need to pass the keys dynamically in the snap. Tried to decrypt with AES Decrypt snap, but the snap has static property for ‘Secret Key’ and ‘initialization vector key’ which has blocked me to pass these 2 values dynamically from upstream snap or params to decrypt the input data. Any suggestion or any other way to do it in Snaplogic, please help.RakeshKumar15 years agoNew Contributor3.8KViews0likes5CommentsUltra pipeline response time
Hi everyone, I’m testing the Ultra feature performance and I’m finding a results that are not so satisfying. Using the new release 4.22 and even the old release 4.21 (including the patches): Simple pipeline containing only JSON Generator snap with the default Hello World output, Bearer token authentication, no query parameters, no additional URL paths in the request. I’m receiving minimum response time of 900 ms (it is sometimes going up to few seconds). I have tested the same pipeline on few organizations and using two REST clients (Postman, Advanced REST Client) but the results are same. Using the older release version 4.20. Few month ago, (I believe it was March) I was testing the same pipeline configuration in Ultra mode and I was receiving minimum response time of 400 ms. I don’t believe that response time of 900 ms is acceptable for such a simple process. Are there any tips and tricks that should be applied on the nodes/snaplex to improve the performance of the pipelines running in Ultra? SnapLogic development team, Is this something that is due to some wrong configurations/setup on my environments or there is a change between the releases that is making an impact on the Ultra performance ?petar_rajchinos6 years agoNew Contributor III3.7KViews1like7Comments