jtonline 110000B6Y8 Marcações:  mdm-developers community group mdm-workbench blog weblog 1.458 Visualizações
This blog itself replaced an earlier website for sharing MDM Workbench news and now it's time to move on again. In fact, this move was prompted by the MDM Developers community which I am really excited about: Raymond discovered that anyone in the MDM Developers group can use the built-in group blog and posted something to help the community. So while there haven't been any posts here this year, there are already a couple of workbench posts on the group blog. Even better, the new blog is better suited to a much wider range of topics and, because anyone in the community can post, it can keep pace with the evolving nature of MDM development.
Please update your feed reader and bookmarks with the new MDM Developers blog!
jtonline 110000B6Y8 Marcações:  profile classpath websphere customer-resources workbench prerequisite faq configelement linux appinstance wiki codegenexception windows7 prereqs mdm-workbench appdeployment webservice-feature-pack group appsoftware mih-workbench 3.413 Visualizações
It's great to be able to announce two new resources for the MDM Workbench:
Platform support and prerequisite software
Can I run MDM Workbench on Linux ?
MDM Workbench is only supported on Windows currently. You may be able to install MDM Workbench on RSA on Linux, and parts of the tool would probably work fine, but the Development and Test Environment wizard will not work.
The Development and Test Environment wizard (often called DEST) is used to install MDM Server on the RSA WebSphere test server, create a database and set up your workspace ready for development. MDM Server is not supported on Windows as a production environment so there is no Windows version of MDM Server. The Websphere AIX version of MDM Server can be installed on Windows using DEST.
Can I run MDM Workbench on Windows 7 ?
We have not tested MDM Workbench on Windows 7. However we are not aware of any problems with MDM Workbench 9.0.x on Windows 7 (with WebSphere 7 and DB2). MDM Workbench 8.5 requires RSA 7.0 which is not supported on Windows 7. WAS 6.1 test server is also not supported on Windows 7.
Why is there a problem setting the runtime for new projects?
To generate web services the workbench requires the Tools for WebSphere Application Server, version 6.1 feature to be installed in RAD/RSA. You must have version 6.1 of the server development tools installed, even if your target runtime is WebSphere Application Server 7, otherwise the following error will occur when generating code:
com.ibm.mdm.tools.models.core.codegen.CodeGenException: Failed to set runtime for new projects: no runtime is associated with the EAR
Errors when running transactions on MDM Server
If you see this error in the WebSphere log when running transactions on MDM Server 8.5, then you have installed the WebSphere 6.1 Web Services Feature Pack. This feature pack is not compatible with MDM Server 8.5.
In a development environment, the feature pack is installed as an optional feature in Installation Manager. Use Installation Manager to uninstall the WebSphere 6.1 test server, then re-install without the Web Services Feature Pack.
If you see this error in the WebSphere log when running transactions on MDM Server, then the server is unable to load configuration settings. The server configuration is stored in the database tables configelement, appsoftware, appdeployment, and appinstance.
First check if the table configelement is empty: if it is, then you need to deploy the server configuration. In a development environment, run the Development and Test Environment wizard task "Deploy configuration to WebSphere profile".
If this does not work, then use the WebSphere admin console to check that the server data sources are defined. If the data sources are not defined, then run the Development and Test Environment wizard task "Configure WebSphere profile". If the data sources are defined, test the connections and address any problems before proceeding.
If there is content in the configelement table, then check the workspace file CustomerResources/properties/config/bootstrap.properties. The property application.manifest.location should be set to the path to the MDM application MANIFEST.MF file, in your workspace. The property deployment.name must match the value in the database table appdeployment.
Common causes of problems
WebSphere application server classpath
In a development environment, the server properties and XSD files are loaded from the CustomerResources project in your workspace. To arrange this, the Development and Test Environment wizard adds the CustomerResources folders to the WebSphere server classpath. If the classpath is pointing to the wrong locations, the server will behave strangely (the exact symptoms will depend on your circumstances).
This can commonly occur if you have tried to copy, move or rename your workspace on the file system or have set up a new development environment re-using an existing WebSphere profile.
To check the server classpath, start the WebSphere admin console. Select the server. On the right hand side of the page, expand Java and Process Management and select Process Definition. Select Java Virtual Machine. You can view and edit the classpath definition in this panel.
To avoid this problem arising: do not copy, move or rename a workspace on your file system and when setting up a development environment, create a new WebSphere profile and make it the default profile.