Validating the Completed Java Application Migration

Objective

After completing this lesson, you will be able to validate the migrated Java application and subaccount configuration against the original SAP BTP, Neo environment landscape to identify and resolve migration gaps using targeted AI prompts for corrective action.

Introduction

In this lesson, you will learn how to verify a successful transition from the SAP BTP, Neo environment to the SAP BTP, Cloud Foundry environment. Validation is a critical phase that ensures both your Java application code and subaccount configurations function as a unified system.

You will utilize a comprehensive validation checklist to confirm that Cloud Foundry modules are running, services like XSUAA are correctly bound, and trust relationships with the Identity Authentication service are active. Finally, you will identify and resolve migration gaps, such as namespace issues or authorization errors, to ensure the application matches the Neo environment baseline functionality.

If Something is not Working

If validation reveals a problem, you can ask the AI to fix it in plain language — no skill names required:

  • Code Snippet
    1
    The application still has javax.* import errors — fix the remaining namespace issues
  • Code Snippet
    1
    The role collections are missing for my test user — reassign them in the SAP BTP, Cloud Foundry runtime subaccount

After each fix, re-run the relevant checklist item to confirm it is resolved.

What Validation Means

At this point in the course you have:

  • Migrated the Java application code and deployed it to Cloud Foundry runtime (Unit 3)

  • Migrated the subaccount trust and role configuration (Unit 4)

Validation is the step that confirms these two tracks have produced a working, correctly configured system — not just that the individual steps completed without errors. A migration is only complete when the application behaves correctly for an authenticated, authorized user.

Validation Checklist

Work through each item below in order. All items must pass before the migration is considered complete.

1. Both Cloud Foundry CLI modules are running

Code Snippet
1
cf apps

Confirm both the Java backend and the Application Router show status running. If either shows crashed or stopped, check the logs before proceeding:

Code Snippet
12
cf logs <your-java-app> --recent cf logs <your-approuter> --recent

2. All services are bound and active

Code Snippet
1
cf services
Confirm the XSUAA service instance is bound to both the Java application and the Application Router. If any service shows as create failed or unbound, re-run the mta-descriptor skill, then run mvn clean package -DskipTests followed by cf deploy . -f.

3. Trust configuration is active

Open the SAP BTP cockpit for your SAP BTP, Cloud Foundry runtime subaccount and navigate to Security → Trust Configuration. Confirm that:

  • The Identity Authentication service tenant appears as a trusted identity provider
  • XSUAA is registered as a Service Provider in the Identity Authentication service admin console (the manual step from Lesson 4.1)

If trust is not yet active, complete the manual steps documented in subaccount-trust-migrator before continuing.

4. Role collections are assigned

In the SAP BTP cockpit, navigate to Security → Role Collections and confirm that:

  • The role collections created by authentication-xsuaa are present
  • Your test user is assigned to the appropriate role collection
  • Any manual checklist items from ~/.neo-migration/$SUBACCOUNT/$CF_SUBACCOUNT_GUID/neo-roles-import-report.json have been resolved

5. Authentication flow completes end to end

Open the Application Router URL in a browser:

Code Snippet
12
cf apps # note the route of the approuter module

You should be:

  • Redirected to the Identity Authentication service login page
  • Able to authenticate with your test user credentials
  • Redirected back to the application after successful login
  • Able to access the application without authorization errors

If you reach the login page but receive an authorization error after login, the most likely cause is a missing role collection assignment or the unresolved Everyone role from Lesson 4.2.

6. Application functionality matches the Neo environment baseline

Compare the behaviour of the migrated Cloud Foundry CLI application against the original Neo environment application. Verify that:

  • Core application features work as expected
  • No javax.* import errors appear in the logs (would indicate an incomplete namespace migration)
  • No JNDI lookup errors appear in the logs (would indicate a missed service binding migration)

If Validation Reveals Gaps

Do not re-run the full orchestrator to fix a specific gap. Re-run the individual skill that is responsible for the failing area:

SymptomLikely causeAction
javax.* class not found errorsIncomplete namespace migrationRe-run jakarta-java25-migration
JNDI lookup failuresMissed service bindingRe-run the relevant skill (destinations, persistence-hana, etc.)
Authentication redirect loopXSUAA not registered as SP in Identity Authentication serviceComplete the manual step in subaccount-trust-migrator
Authorization errors after loginMissing role collection assignmentRe-run subaccount-roles-import or assign manually in cockpit
Service binding errors at startupMissing or misconfigured serviceReview mtad.yaml, re-run mta-descriptor, redeploy

After fixing the gap, re-run the relevant checklist item above to confirm it is resolved.

Summary

  • A migration is complete only when both the Java application code and the subaccount configuration are validated together against the original SAP Neo environment landscape.

  • The six-item validation checklist covers: modules running, services bound, trust active, role collections assigned, authentication flow end to end, and application functionality.

  • When validation reveals a gap, re-run the individual skill responsible for that area rather than restarting the full migration.