| |
Results |
|
No way to update related complex or super package information via web service
|
Updating participating package information on the mainframe side (i.e. through standard XML Services) is deemed a low-level or record-level, yellow service. Execution of the PACKAGE.PRT_PKGS.UPDATE for the complex or super package must be followed by execution of the PACKAGE.GEN_PRMS.UPDATE service for each of the affected participating packages to update the information for all of the affected packages.
|
|
|
|
Product Lifecycle and Platform Matrix
|
On the bottom half of the screen, click the + for one of the items in the list .
|
|
|
|
Troubleshooting communication among SBM Components using Wireshark
|
One way to determine the XML communications being passed between components is through the use of Wireshark. Wireshark captures all data that is sent over a network interface. By default Wireshark is not capable of capturing communications between components that are installed on the same Windows Server because those communications are not sent over a network interface.
|
|
|
|
Approval ID is set incorrectly in the Approval Screen in ZMF when using ARM to integrate with SBM.
|
When using ARM 1.2 to integreate between SBM 2009 R2 and ZMF, using the Approve transition sets the ID in the Approval Screen in ZMF with the ID of the owner where the transition was fired, and not with the ID of the Owner the item is placed. Example: State A (Owner: Tester)====> Approve =====> State B (Owner: Admin)
|
|
|
|
Mainframe Connector Extensions: Mainframe Configuration for accessing ChangeMan ZMF from SBM
|
Please see the following on each of these configuration items .
|
|
|
|
ZMF Hotfix to support ARM 1.1
|
Please refer to the ARM 1.1 documentation for details on the components delivered here.
|
|
|
|
How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
|
It is not necessary for Dimensions CM, Dimensions RM or other Single Sign-on (SSO) enabled products to have user accounts in the SBM database when using the SBM SSO engine. SBM SSO can authenticate users via LDAP. For the purposes of this document, it is assumed that the Single Sign-on enabled product has been setup to point to the SBM SSO engine instead of its own.
|
|
|
RLM HTTP Server Overview:
|
Tomcat will automatically unpack and deploy the war files. If autoDeploy is set to ‘N’, the Tomcat Manager application may be used to deploy the applications individually. The following link points to the Tomcat Manager documentation in detail :
|
|
|
|
ARM 1.2 Hotfix for ZMF 5.6.3 Compatibility
|
was created using TSO XMIT. In order to properly unload it on your mainframe, you must upload the file using the binary transfer method, and unload it using the TSO RECEIVE command. Detailed instructions are found in the document titled $receive.doc.
|
|
|
|
Serena Application Release Manager Installation and Configuration Giude
|
d ForjobsSERSERV and SERTASK, change the dataset names in the sample DD statements to point to the CEXEC library where you unloaded the ChangeMan ZMF SERCOMC installation libraries. e FortheSERCMD job, change the dataset name in the sample DD statement to point to the CLIST library where you unloaded the ChangeMan ZMF SERCOMC installation libraries. f FortheNEWCMD job, change the CLIST library in the sample DD statement to point to the actual REXX execution library where SERSERVC will reside at runtime.
|
|
|
