Zero Bytes

import com.sterlingcommerce.woodstock.workflow.Document; import java.io.InputStream; import java.io.InputStreamReader; import java.io.BufferedReader; Document doc = wfc.getPrimaryDocument(); Document outPutDoc = wfc.newDocument(); ; InputStream inS = doc .getInputStream(); BufferedReader br = new BufferedReader( new InputStreamReader( inS )); String strData = “<SampleData>” ; String strLine; while ((strLine = br .readLine()) != null ) {     strData = strData.concat(strLine); } br.close(); strData = strData + “</SampleData>”; outPutDoc. setBody( strData .toString().getBytes()); wfc.putPrimaryDocument( outPutDoc );

1. Read-Heavy System: Consider using a cache. 2. Low Latency Requirement: Utilize cache and CDN. 3. Write-Heavy System: Use message queues for async processing. 4. ACID Compliance: Opt for RDBMS or SQL Database. 5. Unstructured Data: Choose NoSQL Database. 6. Complex Data (Videos, Images, Files): Go for Blob/Object storage. 7. Complex Pre-computation: Use Message Queue & Cache. 8. High-Volume Data Search: Consider search index or search engine. 9. Scaling SQL Database: Implement Database Sharding. 10. High Availability, Performance, & Throughput: Use a Load Balancer. 11. Global Data Delivery: Employ a CDN. 12. Graph Data: Utilize Graph Database. 13. Scaling Various Components: Implement Horizontal Scaling. 14. High-Performing Database Queries: Use Database Indexes. 15. Bulk Job Processing: Consider Batch Processing & Message Queues. 16. Server Load Management: Use a Rate Limiter. 17. Microservices Architecture: Utilize an API Gateway. 18. Redundancy for Single Point of Fail...

PM interview preparation 1. The only thing that matters by Marc Andreessen : https://lnkd.in/dHYmqkRd 2. Relentlessly resourceful by Paul Graham : https://lnkd.in/d9nGPSFJ 3. Product Management mental models for everyone by Brandon Chu : https://lnkd.in/dzMx4JfW 4. The first principles of product management by Brandon Chu : https://lnkd.in/d4YS_fHi 5. 12 things about product market fit : https://lnkd.in/dyuHB3PC 6. The Minimum Viable Product Manager : https://lnkd.in/d32aBj_y Design thinking process 1. How would you design an interface for a 1000 floor elevator? : https://lnkd.in/dWx2Khxz Building great culture as a PM : 1. How to work with engineers by Julie Zhou : https://lnkd.in/dyY6HsYC 2. How to work with designers by Julie Zhou : https://lnkd.in/dbZCH4cm Execution and Prioritization 1. The time value of shipping by Brandon chu : https://lnkd.in/dvHVpG7D 2. Deadlines by Brandon chu : https://lnkd.in/dNS7ApXh Defensible growth 1. Do things...

 

Here are the some of the Best book collections,  High Performance Habits: How Extraordinary People Become That Way , Hardcover  Getting Things Done : The Art of Stress-Free Productivity by David Allen 52 Red Pills You Can't Order Change The 7 Habits of Highly Effective People Rich Dad Poor Dad  The 4 Hour Work Week High Performance Habits Read People Like a Book Getting Things Done The 80/20 Principle Holy Cow  

First of all the following value has to be unique to each install of Sterling Integrator. If you accidentally used shared location for cluster installation your second node installation not going to work. So here is how we can fix this. 1. Go to user home and move $USERHOME$/IBM/IBMSHARED to new local location. 2. Update the reference in  /home/user/var/ibm/InstallationManager/installRegistry.xml           That's it. This will fix First node IBMSHARED location and we can proceed with second node installation. How to verify? 1. Go to InstallManager tools     cd /InstallationManager/IM_Linux/tools  2. ./imcl listInstalledPackages -verbose Validate the output something like below, [Shared] Shared resources directory: /opt/ibm/IBMIMShared [Package group] Name: Sterling Integrator Installation directory: /opt/ibm/sfg Translations: Architecture: 64-bit [Package] Name: IBM Sterling B2B Integrator (com.ibm.sterling.in...

Some of the IBM Sterling B2B Integrator(SI) customers wants to avoid SSH handshake using CBC Cipher as it is vulnerable. The link  http://www.kb.cert.org/vuls/id/958563  explains that CBC Ciphers are security vulnerable and the solution is to use CTR Cipher instead of CBC Cipher. However, in SI versions 5020602 and 5020603, maverick (the third party api used for SSH/SFTP) version used is 1.4.60 which mandates that CBC Cipher should be present in Client side. Hence, disabling the CBC support using the security property supportCBCCiphers=false will result in SFTP communication failure with key based authentication. To enforce the use of CTR Cipher in SI, we have introduced two new properties : SSHServerCipherList, SSHClientCipherList a) security.SSHServerCipherList is the property to restrict the list of server side ciphers. In the SFTP Server adapter, "Preferred Cipher" drop down will pick the values specified in this property list. b) security.SSHClientCipherList is...