rvsunilkumar

 In this article, focus is more on how to generate server.crt(public key), root.crt and intermediate.crt and how to resolve SSL-PKIX Path building failed error in case the server.crt is not having fullchain.crt that contains - server.crt->intermediate.crt -> root.crt  in fullchain.crt in  sequence file while attaching to DLB. Step 1: Prepare Your Certificate Files the following are needed: Private Key – (signed by CA, can be called as server.key/root.key) Public Certificate – server.crt/public.crt Intermediate Certificate Chain (if applicable) – fullchain.crt (server.crt, intermediate.crt and root.crt in oder of sequence) If there is only server.key/root.key/private.key and public.cert/server.crt how to generate root.crt and intermediate.crt using server.key/root.key/private.key in order to generate certificate-chain.cert that contains sever.cert, intermediate.cert and root.cert if you have private.key(serer.key), follow steps:  generate root certificate usi...

 Scenario: Assuming that there is base64 encoded string containing values separated by tab(\t) and each row is separated by new line(\n) without any headers, how to extract and build json with predefined index mapped to particular attribute name. Lets assume 0 index is firstName, 1st Index is lastName 2nd Index is customerId. Sample Data:   Mule\t Soft\t aa234ed23e Lets encode the above data to base64: TXVsZVx0U29mdFx0YWEyMzRlZDIzZQ== Now using dataweave functions read, fromBase64 and valueOf ,  extract and build json.

  Key Differences Between SOQL and SOSL Feature SOQL (Salesforce Object Query Language) SOSL (Salesforce Object Search Language) Purpose Retrieves records from a  single object or related objects . Searches for text across  multiple objects and fields . Use Case Use when you  know the object and fields  you want to query. Use when you  don't know where the data is  (full-text search). Scope Works on  one object at a time  (or related objects via relationships). Searches  multiple objects at once . Search Type Structured  query-based search . Full-text  keyword-based search . Works With Standard/Custom objects, Fields (SELECT queries). Indexed text fields, Name fields, Email fields. ...

When designing data flows, choosing between pushing (sending data proactively) and pulling ( retrieving data on demand ) depends on factors like efficiency, latency, scalability and control.  Pushing Data: The source system sends data automatically to the destination as they occur. Pros of Pushing Data : Lower Latency: Updates are delivered in real-time or near real-time. Efficiency for High-Frequency data: Reduces the need for repeated requests when data updates frequently. Less Client-side Processing: The destinatiuon system doesn't need to monitor or poll for changes. Reduces Server Load (for clients). Eliminates unnecessary requests when no new data is available. Cons of Pushing Data: Potential Overload: if too much data is pushed once, the receiver may struggle to process it efficiently. More Complex Error Handling: if the destination is down, data might be lost without a proper retry mechanism. Requires Efficient Event Handling:  The destination must be able to hand...

MuleSoft Blog on PGP https://blogs.mulesoft.com/dev-guides/mule-pgp-encryption-gnugp/ There are eight processors related to PGP in Mulesoft , apart from PGP Global Configuration at this time of writing. 1. Pgp Encrypt 2, Pgp Encrypt and Sign 3. Pgp Encrypt binary 4. Pgp Decrypt 5. Pgp Sign 6. Pgp Sign binary 7.Pgp Validate 8. Pgp Binary to armoured. About Pretty Good Privacy (PGP)  In the context of Pretty Good Privacy (PGP) and its implementation GnuPG (GPG), key listings use specific abbreviations to denote different types of keys: sec : Secret (private) primary key ssb : Secret (private) subkey pub : Public primary key sub : Public subkey Key usage flags indicate the specific purposes for which a key can be utilized. These flags are represented by single-letter abbreviations: S : Signing C : Certifying (issuing certifications for other keys) E : Encrypting A : Authentication When you see a key with the usage flags SC , it signifies that the key is designated for both signing and...

 Refer Mulesoft blog link provided below  on how threading works in mule4, refer the scenarios presented for detailed understanding of different thread pools, switching and behavior. Broad Topics Covered: Centralized thread pools HTTP thread pools Thread pool responsibilities Thread pool sizing Thread pool scheduler assignment criteria Mule runtime example consumption of thread pools Typical thread switching scenario - usecases https://blogs.mulesoft.com/dev-guides/how-to-tutorials/thread-management-auto-tuning-mule-4/

 Here we will look at how Update SQL query with IN clause can be constructed when there are multiple values coming as array as IN clause input Assuming that dateSent must be updated for all the eventIds sent as input using IN clause. Input: { "dateUpdated" : "2025-01-14" , "eventId" : [ "234er-4356" , "234er-4896" , "4dse4-4321" ] } Building Update SQL in Dataweave %dw 2.0 output application/json --- { "dynamicUpdateStatement" : "Update table_name set dateSent='" ++ payload . dateUpdated ++ "' where eventId in (" ++ "'" ++ (payload . eventId joinBy( "','" ) ++ ")" ) } Output: { "dynamicUpdateStatement" : "Update table_name set dateSent='2025-01-14' where eventId in ('234er-4356','234er-4896','4dse4=4321')" } Screenshot: Another Solution: Dataweave: %dw 2.0 output application/json ---...