Implement change control as part of your development process. Integrate your change control system with SAP Mobile Platform. Ensure that all your development artifacts are routinely checked into your change control system, so you can revert back to a known version if necessary.
Eclipse includes a built-in client for the Concurrent Versions System (CVS). See the Eclipse FAQ to learn more:http://wiki.eclipse.org/index.php/CVS_FAQ. You can also integrate other source control systems, such as Subversion.
When implementing change control:
- Set up the repository for the shared development
environment.
- Identify the artifacts to be maintained as source code, for example:
- Model files (the Mobile WorkSpace project file)
- Native application code, and generated and custom client
code
- Mobile WorkSpace artifacts, which are the MBO projects,
custom result checkers, enterprise information system (EIS), and model
files
- Custom ResultSet filters and error checkers
- EIS connection profiles
- Projects
- Identify and communicate change control policies and procedures
to the development team.
Note: Treat the MBO model files, sup.model and
sup.model_diagram, as binary files when using a 3rd party change control
plugin. Do not use the compare and merge utility from the change control plugin to
manually merge the model files at the xml source(text) level, since it may render
the models inconsistent and fail to function properly.