Thank you very much for the clarification and for sharing your experience - this really helps me understand how to separate installation and implementation effort more realistically.
And yes, you are correct: I'm currently preparing an offer as part of a consulting engagement.
That's why I'm gathering as much community guidance as possible - especially around effort estimation, architectural considerations, and whether some components can be reused across use cases.
If you have any additional suggestions on how to size these scenarios or structure the POC, your feedback would be greatly appreciated.
Thank you again for your support.
Original Message:
Sent: Thu December 11, 2025 11:36 AM
From: Engin Sarlak
Subject: Guidance Needed for Implementing webMethods Use Cases on OpenShift
You should estimate installation and implementation seperately. Your enviroment will depend on your use case I agree, but it depends on your contract first. If you don't have a contract yet, start with a POC. implement one of the scenarios, and review what you could do better. Clean your work and then check if you can reuse some of the componnents you implemented.
Implementation and installation estimates depend on the person who works on that task and the complexity of the architecture. Typically implementing a webservice or calling it from webmethods is pretty simple once you get used to it. If you use webMethods.io you won't have to do the installation manaully, which will consume a lot of time if you do it yourself. For me it takes around a week per environment, but I wouldn't be surprised if someone else estimates a month per environment.
Let start from the begining first. I presume you work in a consulting firm and you need to prepare an offer. Correct me if I am wrong. So, does the company you are preparing the offer for, have any webmethods license? If they have, this will be your biggest strength.
------------------------------
Engin Sarlak
Original Message:
Sent: Thu December 11, 2025 10:25 AM
From: Jason Rick Medina Arbi
Subject: Guidance Needed for Implementing webMethods Use Cases on OpenShift
Hi engin sarlak
Thank you very much for your feedback - and absolutely, I agree with your point.
Just to clarify:
I'm not looking for a finished product or for anyone to build the solution. What I'm trying to understand is the typical effort range (hours) for use cases of similar complexity, since I'm still new to webMethods and want to ensure that our estimation is realistic.
I fully understand that each implementation will vary, and that the real work must be done by the project team. My goal is simply to gather reference points, best practices, and lessons learned from people who may have implemented similar patterns before.
I really appreciate your recommendation about using the webMethods helm charts and considering webMethods.io for webhook-driven integrations - that's very helpful for validating the architecture approach.
If anyone has guidance on:
How you normally estimate effort for integrations in webMethods
Typical hour ranges for similar use cases
Key activities that usually impact the effort
Or even red flags to consider while sizing the work
it would be extremely valuable.
Here are the architecture diagrams for each use case. I included the detailed scope of what will be done in each one. Could you please provide your feedback?
Thanks again for the insights!
------------------------------
Jason Rick Medina Arbi
Original Message:
Sent: Wed December 10, 2025 07:16 PM
From: engin sarlak
Subject: Guidance Needed for Implementing webMethods Use Cases on OpenShift
It looks like you are looking for a finished product rather then a guidance. I recommend splitting your requirements in to more managable chunks.
You can use webmethods helm charts to build your cluster. This will make your orchestration simpler but the cluster initialization can be frustrating at the begining. Try not to forget to commit and push your changes whenever you have a working values.yaml. Using openshift, kubernetes or rancher shouldn't make any difference here though you are talking about webhooks and such, so it might be better if you use webmethods.io instead. Some of the connectors and webhooks should already be defined there, and even if not, itsn't that difficult to create it. The rest of the things you are asking for are the actual work and I doubt anyone will have anything ready or do it for you. Try to picture the design you have in your mind and ask for feedback instead.
------------------------------
engin sarlak
Original Message:
Sent: Fri November 28, 2025 03:43 PM
From: Jason Rick Medina Arbi
Subject: Guidance Needed for Implementing webMethods Use Cases on OpenShift
Hello everyone,
I'm currently reviewing a technical proposal involving several webMethods integration flows running on OpenShift. I would really appreciate any guidance, step-by-step examples, best practices, or similar use cases that can help us structure the implementation correctly.
Below are the three use cases exactly as defined in the scope document, so the community can help point me in the right direction.
πΉ Use Case 1 β Certificate Orchestration (Zendesk + GitHub + Node.js)
Process where financial institutions submit digital certificates for secure communication.
Scope details:
Install webMethods Integration Server on OpenShift:
DEV: single instance
PROD: two-node cluster
Implement:
Zendesk connector
GitHub connector
Node.js certificate handling service
Build the main orchestration workflow for certificate processing.
Functional end-to-end testing.
Promotion to production.
Technical documentation (design, deployment, operations).
What I need from the community:
Examples of certificate orchestration workflows in webMethods.
Guidance or samples for integrating Zendesk and GitHub connectors.
Best practices for using or integrating Node.js services with webMethods.
Similar use cases you may have implemented.
πΉ Use Case 2 β Automated CSV Report Generation and Delivery to AWS S3
Process that extracts data from PostgreSQL, generates CSV files, and sends them to an S3 bucket.
Scope details:
Configure connectivity to PostgreSQL (PgSQL).
Implement logic to generate CSV reports.
Upload the generated files to an AWS S3 bucket.
Configure MFT Virtual Folder + Web Client for user access.
Testing and validation.
Technical documentation and deployment package.
What I need from the community:
Examples of PostgreSQL data extraction in webMethods.
How to dynamically generate CSV files inside Flow Services.
Step-by-step guidance for AWS S3 integration.
Examples of configuring MFT Virtual Folder in webMethods.
πΉ Use Case 3 β Availability Monitoring and Alerts
Process that receives event payloads (errors/latency) and triggers email/Teams notifications.
Scope details:
Create an Event Listener in webMethods (REST/webhook trigger).
Develop Integration Flow Services to process the alert payload.
Implement outbound notifications for:
Email
Microsoft Teams (webhook)
Build outbound connectors.
Unit testing + end-to-end testing.
Documentation and deployment package.
What I need from the community:
Examples of Event Listeners (REST/webhook) in webMethods.
Guidance on designing alert-processing Integration Flows.
How to implement Teams + email notifications.
Best practices for event-processing and alerting patterns.
π Request for assistance
I would really appreciate:
Step-by-step tutorials or guides
Flow Service examples
Similar use cases implemented on OpenShift
Architecture recommendations
Best practices for connectors and integration patterns
Thank you very much in advance - any help or shared experience will be extremely valuable!
------------------------------
Jason Rick Medina Arbi
------------------------------