What kind of java skills are required for developing solutions using webMethods Integration

[reamon]

“What kind of java skills are required for developing solutions using webMethods Integration [Server}”

Short answer: None. One does not need to know Java at all to be effective using wM IS to develop solutions. As @Holger_von_Thomsen notes, it is not a prerequisite and the primary language for wM IS is FLOW.

Long answer: Knowledge of Java and the various related components noted by @sahasakhar934 and @ethanklein can be very useful but is not required. There are many discussions on the forums about FLOW vs. Java. Here are a couple of them for consideration. Old but still applicable.

Java Development Estimates

Can anyone give me an estimate on the amount of Java development required for a given integration project using wM (IS, EB, etc.)

Integration Server and Java

It may just be my perception but it seems like there has been an unusual number of questions about how to do things in Java within Integration Server. I thought I’d post a gentle reminder of the three guiding principles of Integration Server development: Don’t write it in Java. Don’t write it in Java. Don’t write it in Java. Of course that’s an extreme point of view but it’s worth keeping in mind. There have been various discussion threads over the years about the use of Java services…

IMO, a significant reason why wM IS is even still around is because one does not need to be Java programmer to be productive with it. Knowing Java is certainly helpful, but not necessary.

Use of Java is secondary, not primary. A common use of Java is “small java services to provide utility-like functions.” Often, just wrappers around core Java classes/methods.