#MuleSoft토론 중인 항목 26개

Modernise your middleware for your Integration Era: 

Discover how MuleSoft helps you modernize aging middleware, Spring Boot apps, and legacy ESBs into a governed, AI-ready integration backbone, without disrupting what already works. Explore the resources below to go deeper on architecture, governance, and real-world modernization patterns. 

• Legacy Modernization and APIs: Pathways to Agentic AI Success
• A Framework for Architecting Agent Control Plane
• Architecting the Agentic Enterprise: Unifying Context, Control and Activation for AI Agents
• Going Headless: Architecting for the Age of Agents

• Stop a Rogue Agent in Seconds: Agent Kill Switch is Now GA
• MuleSoft Platform MCP Server: Turn API Operations Into Natural Language

• On-Demand Webinar: Navigate the Path to Agentic Through APIs and Legacy Modernization (with Deloitte)
• Webinar: Three Proven Moves to Modernize Legacy Systems with MuleSoft

#MuleSoft  #API  #Trailhead  #MuleSoft Community Posts  #Middleware

Using Anypoint Code Builder with agent-fabric-transformation 1.6.0 (agent-network.yaml, agentNetwork: 2.0.0).

Every Deploy logs this warning for my AgentScript broker:

Warning: Broker 'customer_support_broker' does not declare an 'authorization' configuration, so it will fall back to the 'user-context-propagation' policy defaults: userIdExpression '#authentication.clientId' and allowAnonymousAccess true (requests whose principal cannot be determined are forwarded anonymously). To change this, set authorization under the broker's interfaces.a2a section, e.g.:

brokers: 

    customer_support_broker: 

       interfaces: 

          a2a: 

             authorization: 

                 principal: '

' 

                 allowAnonymousAccess: false 

At runtime this also throws a recurring "User ID expression resolved to invalid non-string value" warning, since I have no Client ID Enforcement policy configured (I don't need real caller identity — this broker isn't meant to authenticate clients).

Problem: following the warning's own suggested fix fails Build validation:

Message: brokers/customer_support_broker/interfaces/a2a must NOT have additional properties

So authorization isn't actually a field the current agent-network.yaml schema (v2, as validated by agent-fabric-transformation 1.6.0) accepts under interfaces.a2a — it only allows card and policies.

I then tried explicitly declaring the policy under policies.inbound instead:

brokers: 

     customer_support_broker: 

         interfaces: 

             a2a: 

                 policies: 

                     inbound: 

                         - policy: 

                             ref: 

                                 name: user-context-propagation 

                                 namespace: 68ef9520-24e9-4cf2-b2f5-620025690913 

                             configuration: 

                                 userIdExpression: '

' 

                                 allowAnonymousAccess: true

(namespace taken from the groupId on the built connection.json's policyRef for this same policy). This passes schema validation but fails with:

Cannot resolve reference user-context-propagation of kind policy (http://a.ml/vocabularies/data#invalid-reference-like)

Questions:

1. What's the actual supported syntax to override this auto-injected default policy's configuration from agent-network.yaml?
2. Is the authorization block from the warning message a planned/upcoming field not yet implemented in 1.6.0, or am I missing something?
3. Alternatively, is there a supported way to just suppress the userIdExpression warning without adding real Client ID Enforcement?

Happy to share the full agent-network.yaml if useful. 

【Trailhead Academyより、MuleSoft新コース開始＆既存コースの名称変更に関するお知らせ 】

MuleSoftの新コース提供の開始、およびコース名変更のお知らせです。

＜新コース提供開始のご案内＞

Anypoint Code Builder (ACB) 対応版の開発基礎コースが正式リリースとなり、コースの公開と申し込み受付が始まりました。 

• コース名・申し込みページはこちら：
  • MuleSoft 開発基礎 (Anypoint Code Builder) [前編] - DEX406-1
  • MuleSoft 開発基礎 (Anypoint Code Builder) [後編] - DEX406-2
• 初回開催日程：2026年11月9日(月) ～ 11月13日(金)
• 本コースの特徴：Anypoint Code Builderを用いたMuleSoftの開発フローを実践的に学習します。参加者自身の環境に縛られることなく、より手軽にハンズオンの学習・体験が可能になります。

＜コース名変更のお知らせ＞

 下記3コースにつきまして、コース名が変更されましたのでお知らせします。*コース内容に変更はありません。

•  「Anypoint Platform Development: Production-Ready [前編] 開発ベストプラクティス（DEX660）」は下記に変更になりました。
  • 新：MuleSoft 開発上級 (Anypoint Studio) [前編]（DEX660）
• 「Anypoint Platform Development: Production-Ready [後編] インテグレーション・ベストプラクティス （DEX670）」は下記に変更になりました。
  • 新：MuleSoft 開発上級 (Anypoint Studio) [後編]（DEX670）
• 「Anypoint Platform Architecture: Integration Solutions (インテグレーションソリューションズ) （ARC730）」は下記に変更になりました。
  • 新：MuleSoftアプリケーションアーキテクチャ基礎（ARC730）

@* カスタマーサクセス日本 *

#MuleSoft  #MuleSoft Training & Certification

• You are trying to connect your Salesforce org to Anypoint Platform.
• You are receiving the error: "Organization is not yet onboarded to GDoT."
• Request backend provisioning or onboarding for your Salesforce org to GDoT.

#Salesforce Admin  #MuleSoft Anypoint Platform  #Einstein For Service  #MuleSoft

Updates to Slack’s plans and pricing

Hi Slack Community: I’m writing with some important updates to Slack’s plans and pricing.  

We are committed to giving every team an onramp to AI-powered productivity in Slack, and every organization a secure foundation to grow with digital labor. As such, pricing has been simplified, delivering new features across every plan. 

Features highlights

• AI features are being integrated across all paid plans. 
• AI agents from Agentforce and partner AI apps can now be deployed in all paid plans
• Every Salesforce customer will get Slack’s free plan, with access to the brand new Salesforce Channels feature, bringing Slack and Salesforce even closer together.
• We’re enhancing security across all plans, bringing session duration controls and native device management to all of our plans, including Free, and adding SAML-based SSO for Salesforce customers — giving every team a trusted foundation to securely connect their people, data, AI, and agents.

Pricing highlights (Read more about the plans on the Slack Plans page)

• Free subscribers will maintain access to their current features and will gain access to Salesforce channels.
• Pro pricing will stay the same and will now include core AI features, Salesforce channels and enhanced security. 
• Business+ plan pricing will increase to $15 from $12.50 per user per month to reflect the significant value added through new advanced AI capabilities and premium Salesforce integrations.
• We are introducing a new Enterprise+ plan which includes enterprise search in addition to the full Slack feature set including enterprise-grade AI, premium Salesforce integrations and enhanced security, admin controls, governance and compliance (contact your sales rep to learn more).

🔗 LEARN MORE

#Slack Community #TrailblazerCommunity #MuleSoft #Tableau

☁️ Salesforce Developers — Ready for Your Next Adventure? 🚀 

Innovate! Inc. is looking for a Mid-Level Salesforce Developer to join our team and help build scalable, user-focused Salesforce solutions. 

If you enjoy turning business requirements into great Salesforce experiences and have hands-on experience with Experience Cloud, Apex, LWC, Flow, and integrations, this could be a great next step! 💻✨ 

🔹 What we’re looking for:

☁️ 3+ years of hands-on Salesforce development experience 

🌐 Hands-on Experience Cloud development, including authenticated external-user experiences 

💻 Experience with Apex, Lightning Web Components, Flow & SOQL

🔗 Experience developing or supporting REST/SOAP integrations

🛡️ Understanding of Salesforce security, sharing, profiles, permission sets & external-user access 

🧪 Experience with code reviews, testing, troubleshooting & production support 

🚀 Familiarity with Git, Salesforce CLI/SFDX, deployments & CI/CD processes 

🤝 Ability to collaborate with business analysts and technical teams to build scalable solutions

➕ Experience with Service Cloud and MuleSoft is a plus!

🏅 Preferred certifications include Experience Cloud Consultant, Platform App Builder, Platform Developer I, and JavaScript Developer I. 

🏠 Remote within the U.S. 

💰 Salary Range: $100,000–$120,000 

🇺🇸 U.S. Citizenship required

 🔐 Must be able to obtain a Public Trust clearance

📋 Position is contingent upon contract award. 

Interested? Take a look! 👇 

👉 Learn more and apply:

https://innovateteam.my.salesforce-sites.com/InnovatePublicJobBoard/PublicJobPosting?id=a1KVJ00001nrZKf2AM

And if someone in your Trailblazer network comes to mind, please tag or share! 🙌☁️ 

#Jobs #Salesforce Developer #Experience Cloud #MuleSoft #Lightning Web Components #Remote Opportunities

Hi, the current version of the SAP JCo connector enforces the name of the containing jar at runtime. 

This will lead to exceptions, if it doesn't match the name (sapjco3.jar).

JCo initialization failed with java.lang.ExceptionInInitializerError: Illegal JCo archive "com.sap.conn.jco.sapjco3-3.1.13.jar". 
It is not allowed to rename or repackage the original archive "sapjco3.jar".
Caused by: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.ExceptionInInitializerError: 
Illegal JCo archive "com.sap.conn.jco.sapjco3-3.1.13.jar". It is not allowed to rename or repackage the original archive "sapjco3.jar".

This is a known issue described in the documentation: 

-

-

To resolve this error, the maven-shade-plugin should be added to pom.xml which relocate (rewrite) packages to avoid classpath conflicts. Unfortunately, this approach works only at runtime, but not for MUnit tests. Does anyone know how to configure the pom.xml file for the MUnit tests?