SRM-MDM Netweaver Upgrade

Does anyone know of any reason why we can not upgrade Netweaver 7.0 from SP 14 to SP20 for our server running the SRM-MDM Catalog.  All of the documentation states min requirements but no max.
We are currently running SRM-MDM Catalog 2.0 SP4 Patch10 on Netweaver 7.0 SP14

Hi Mike,
Kindly go trough the below link which explains the advantages of using SRM 2.0 over 1.0 vrs.
The blog also has links in between such as:
https://websmp204.sap-ag.de/instguides
which will guide you on what to follow for the upgrades.
Hope It Helped
Thanks & Regards
Simona Pinto

Similar Messages

  • Pictures not appearing in after upgrade to SRM-MDM Catalog 3.0 SP7 Patch4

    Hello,
    Due to some issues in Advanced search we performed the service pack upgrade from SRM-MDM Catalog 3.0 SP5 (with MDM 7.1.03.72) to SRM-MDM Catalog 3.0 SP7 Patch4 ( MDM 7.1.04.146).  With this new SP, the Pictures are not appearing anymore under the Hyperlink section anwhere in Catalog browser( Compare, Context view, Item details). With earlier SP pictures were appearing perfectly.
    We have done like this:( refer earlier thread - Re: SRM MDM Catalog 3.0 Image display) thanks Sudhanshu, Jitesh and Mandeep for suggesting that solution!
    Using the hyperlink field
    type : rendered
    MIME type : image type i.e. .jpg
    URL : web URL
    We had gone for this option because we dont want to store impages in MDM, and this worked perfoectly until new SP upgrade.
    Any clues?
    Thanks
    Pravin

    Hi Bala,
    Nothing appears under the Hyperlink section in Catalog browser, though a valid link exists in Data Manager under Hyperlink  as type-Rendered, MIME type as JPG and a valid URL.
    I have searched Service Market place for this fix of this issue and found that SAP has improved the technology ( from Object Cache to Blob Cache) to display pictures/hyperlinks from SRM-MDM Catalog 3.0 SP06 and MDM 7.1SP04 onwards. We were  on SRM-MDM Catalog 3.0 SP05 and MDM 7.1 SP03 before Dev upgrade.
    Here are the notes for reference of others who get into same issue.
    Note 1450593 - Implementation of BlobCache
    This note states "MDM7.1 SP04 offers new image caching functionality called Blob Cache. The old functionality of Object Cache is replaced with the Blocb Cache mechanism in Catalog 3.0 SP06 P1"
    Note 1505796 - Images not showing in SRM-MDM catalog (error in BlobCache)
    This note talks about the issue in MDM API with Blob Cache. The Fix has been provided in SRM-MDM Catalog SP08 Patch 01.
    But upgrade is not something that happens on the drop of a hat, we dont want to do another upgrade,  I would like to know if there is a workaround.
    Thanks
    Pravin

  • SRM-MDM V2.0 on SRM 4.0 Netweaver 2004

    Dear Experts, is SRM-MDM Catalog V2.0 supported on SRM 4.0 (SRM Server 5.0) running on Netweaver 2004. The link service.sap.com/ibc-srm -> mySAP SRM-> SRM-MDM Catalog- > master guide only has details for SRM 5.5. Can you please let me know if SRM-MDM is an option for SRM 4.0 (without XI) or only support CCM2.0. Thanks in advance.
    Regards
    Gabriel

    Hi Gabriel,
    SRM-MDM 2.0 can be used with SRM 4.0, SRM 4.0 was delivered with SAP CCM this is why you do not see anything in the SRM 4.0 master guide.
    There are certain functionalities which will not be avaiable to you using SRM 4.0 however in general, as the catalog application is not integrated with the SRM SERVER it is usable.
    Please note that if you do not have SAP XI then you cannot avail of the product master data transfer/contract data transfer and ERP integration will not be possible.
    Regards.
    Jason

  • CCM 2.0 Catalog to SRM-MDM 3.0 Catalog during SRM 7.0 upgrade

    Hi,
    We are upgrading our existing SRM 5.0 system to SRM 7.0 and we are planning to deploy SRM-MDM 3.0 Catalog as it is more flexible & SAP is not going to support CCM 2.0 Catalog after 2013. Please let me know the upgrade steps/plan to upgrade CCM 2.0 to SRM-MDM 3.0 catalog. As per my understanding, there is no tool/method available to upgrade from CCM 2.0 to SRM-MDM 3.0 catalog available. We need to build it from scratch i.e maintain SAP supplied MDM repository, upload data from SRM/ERP, upload suppliers catalog etc.
    Thanks,
    AS

    Hi,
    I have migrated CCM to SRM-MDM Catalog.
    Steps are
    - Install SRM-MDM Catalog
    - Adjust Repository if you have custom fields
    - Import contents
    - Adjust view
    Migration itself is not difficult but you need to learn how to use MDM client tools.
    The SRM270 class room training is good one.
    http://www.sap.com/usa/services/education/catalog/globaltabbedcourse.epx?context=%5b%5bSRM_SRM_NA%7cSRM270%7c%7c%7c%7cUS%7c%5d%5d%7c
    Regards,
    Masa

  • Upgrade from CCM 1.0 to SRM-MDM 3.0

    At present  we are using CCM 1.0  with  SRM 4.0 and in the process of upgrading it to SRM-MDM 3.0  catalogs. All the internal catalogs needs to upgraded to MDM 3.0 from CCM 1.0.
    Could somebody explain the steps to follow to achieve this.
    Thanks for your help.

    Hi,
    It is not upgrading the system. It is new installation and contents migration.
    1. install SRM-MDM Catalog
    2. import contents
    3. define views (namedsearch/mask in MDM)
    Please check the SRM-MDM Catalog installation guide.
    http://service.sap.com/srm-inst -> SRM Server 7.0
    Regards,
    Masa

  • SRM 5.5 upgrade to SRM 7.0 with MDM

    Hi,
    Pl consider the following scenario and give your views.
    Our client has SRM 5.5 running with SRM MDM 2.0 in their landscape. Now they wish to upgrade to SRM 7.0 without upgrading MDM.(We are upgrading through the parallel landscape).
    So during the upgrade phase, we wish to connect SRM 5.5 and SRM 7.0 both to their existing MDM system for testing purpose. Is this possible?
    PS : Parallel landscape is existing DEV environment will be copied and then upgrade the copied environment. We plan to copy only SRM Server and want to continue using the existing MDM, PI, Portal and TREX setup.
    Regards

    Hi,
    No issue for testing purpose in test landscape. It is not production usage and production system.
    Regards,
    Masa

  • Limitations of SRM-MDM by NOT using Windows + SQL Server

    Hi all,
    our consultants told us, that there are some sort of "limitations" if we install SRM-MDM other platforms than Windows + SQL Server; as example we were told, that e. g. the upload of BMECat files is not possible.
    Is that true? If yes, where can I get a full list of "platform dependent" limitations?
    We don't want to go for Windows nor SQL-Server if possible at all...
    Thanx!
    Regards,
    Markus

    Hi
    <u>Incase you are using SRM 6.0, then -></u>
    SAP SRM 6.0 is a big step forward for SRM: SRM 6.0 is the first SAP software to rely on the new user interface technology WebDynpro and the Web Application Server, rather than the previous ITS. It is also based on the completely new business rule framework (BRF) to define approval workflows. These changes are intended to improve usability and simplify workflow administration / customization, leading to better acceptance and lower TCO for our customers. However, the move to these new technologies is also a complex change and as a result, the product has experienced delays.
    With our most recent development milestone - service pack 2 in mid-July 2007 - we have made lots of progress towards completion; however, we estimated that the product was still not yet ready for Ramp-Up. As a result, we decided to release the product only in beta shipment and to a very limited set of customers (14 in total) who are being closely monitored by our development organization. Seven of these customers are actually planning to go live on the current beta shipment.
    Based on the progress made so far with Service Pack 2, we feel that we should be able to start the official Ramp-Up process on December 10th, 2007 - the target ship date for Service Pack 03. By that time, we should already have 3+ live customers, so new customers starting their projects will benefit from the experiences acquired from previous implementations.
    <u>Time plan and Recommendations</u>
    1. Ideally, we recommend that new and upgrade SRM customers wait for the start of Ramp-Up for SRM 6.0 SP03 (Dec 10th, 2007) rather than starting a project with the previous release SRM 5.0. SRM 6.0 offers many benefits compared to SRM 5.0 and should be easier to use + maintain. An Online scoping questionnaire will be available from mid October in the SAP Service Marketplace as usual.
    2. The number of Beta shipment customers is strictly limited and therefore we do not intend to ship Service Pack 2 to any additional customers besides the 14 customers currently in Beta.
    3. Implementation partners can request a demo license of the current support package 2 in the partner portal. They can set up their sandbox systems and familiarize with the new technology upfront before they enter into customer projects from Dec. 10.
    "Should you have any further questions please contact your local SAP account executive"
    <u><b>Also Please have a look at:</b></u>
    <b>https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000692229&</b>
    <u>Target Release to customer: Q4, 2007
    Target Completion date Ramp-Up: Q1, 2008</u>
    Re: What is MDM?
    https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=3226958
    Getting Started with SAP NetWeaver Master Data Management [original link is broken]
    https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=1757063
    https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3408029
    https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=2857409
    https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3442957
    https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3687977
    Re: Is SRM 6.0 (SRM 2007) released for non-ramp up customers?
    Config UI not change
    Do let me know.
    Regards
    - Atul

  • ECC TO SRM-MDM CATALOG THROUGH SAP PI

    We have a scenario where we are sending data from ECC to SRM-MDM Catalog through SAP PI and data is coming from ECC through proxy and sending to SRM u2013MDM catlog through file adapter. In ESR part we have used SAP defined standard service interfaces (CatalogueUpdateNotification as sender interface and MDMInfoRecordDataTransmission as a receiver interface). The mapping used is also standard one.
    Now we have got requirement to send the data for vendor mat no, manufacturer field of info records from ECC to SRM-MDM catlog.  But we are unable to find out these two fields in standard interfaces/messages. Can anybody guide us how to add these fields in the current data types or is there any other standard interfaces we can use.
    Thanks in advance.

    Hi Shiv,
    Many thanks for your reply.
    Since we're not using XI / PI scenario and this is an upgrade from SRM 5.5 to SRM 7, Iu2019m using the same approach that was already used in SRM 5.5 with CCM 2.0.
    The idea is that the catalogue and all the records maintained need to be associated to a contract. So, I add the contract ID and the correspondent contract item in the import file, in addition to the supplier name, product ID, price information and so on. I mapped the contract ID with the field contract price.
    In relation to the price information fields, as I want it to be visible for any user that accesses the product catalogue, I tried different approaches:
    1.Using OCI Price information u2013 amount, currency, price base quantity and price base quantity UoM;
    2.Using OCI Price contract u2013 amount, currency, price base quantity and price base quantity UoM;
    The first approach didnu2019t work very well, as I was not able to see price information when accessing the catalogue. I could only see it once I transfer the items to the SC. In addition, this approach had one problem. The products were displayed but it was not possible to select the items one by one. To do that I needed to select all the items of the catalogue and after that the detail of the contract ID was displayed in every item, allowing me to choose the items that I want to select to my SC.
    The second approach was better as the information was visible when accessing the SC and I was able to select all the items, one by one, as it should be. The main problem of this approach was that Iu2019m getting errors in the SC when the materials have stock u2013 u201CInterface data contains errorsu201D. Or alternatively, if the items didnu2019t have stock, the SC was possible, but when I tried to create a PO from that SC, It simply does not work.
    So, can someone help me? Any ideas?
    Thanks in advance.
    Best regards,
    Andreia

  • SRM MDM catalog items not checking back to EBP ("500 Internal Server Error")

    Hi All,
    We are having an issue, ONLY with our PRODUCTION environment.
    When we create a Shopping Cart and select items from an Internal catalogue, we cannot check the items back into SRM without the system throwing the "500 Internal Server Error" message. As the items never even reach SRM, there is nothing to check or display in the queues for anything even remotely helpful.
    As mentioned above, the issue is only happening in our Production environment. We have tested using the production MDM webservice details in our PreProd environment and everything works flawlessly, so the issue very likely arises from our Production portal.
    System info:
    We have SRM 7.2; SRM MDM 3.0 and SAP Netweaver portal 7.1.
    The users are using IE9 but the same happens on IE8 as well.
    We have checked and all MDM applications are running.
    We have done all the compatibility checks too given in https://scn.sap.com/thread/1075870  and https://scn.sap.com/thread/1836750 .
    I have attached the logs.
    Nothing helped so far, so we are hoping maybe either of you can.
    Thanks in advance,
    Niki

    Hi Jason,
    So in the end SAP gave a response that worked.
    We actually had to delete the BYPASS_INB_HANDLER parameter and change our URL slightly. That helped and now the items check back in to EBP without issues.
    The strange thing is that we still have that parameter in every other environment and yet it still works flawlessly, only causing issues in PROD. We are waiting on a response from them to ellaborate why... I am going to share when they respond.
    Thank you for all the help!
    Bests,
    Niki

  • Multiple SRM Systems One SRM-MDM Catalog?

    Hi
    I'm currently upgrading our SRM 5.0 to SRM 7.01 with SRM-MDM Catalog 7.01.  Is it possible to use one SRM-MDM Catalog in our non-production environment and connect multiple SRM systems to it?
    For example our sandbox, development and QA SRM 7.01 systems would all connect to the same SRM-MDM Catalog 7.01.
    Thanks.
    Neil

    Hi,
    for non-production use and if it is just a catalog without custom coding running I see no problem in using one MDM server for multiple SRM systems (especially sharing one for sandboxes and dev). It is a setup I have seen multiple times and it worked always without problems.
    You should set up different repositories for each SRM system so that you don't interfere with each others data (i.e. suppliers or other lookups tied to SRM).
    You have to keep in mind that you have to upgrade all systems together. But you can always use separate MDM servers during the upgrade process and then consolidate onto one server when the upgrade is done.
    If you are running custom coding with your MDM catalog I would recommend having a separate MDM system for the QA SRM in order to be closer to the production set-up when testing your custom solution.
    Regards,
    Martin

  • SRM-MDM 3.0, assignment failed, runtime error

    Hi all,
    We are using SRM-MDM catalog 3.0, MDM-Client version are 7.1.01.78.
    When building assignments which include lookup tables, the assignment failes giving the following runtime error:
        "Assignment operation failed: A runtime error occurred while evaluating an validation or calculation field"
    The assignment is initialising the item type with "Normal". If it is already filled, leave the old value.
    Assignment Code Used:  IF(IS_NULL(Item Type.[[Record]]), Item Type [[Normal]],Item Type.[[Record]])
    The runtime error only occures when the Else-branche is processed.
    This code above is also used in version 2.0 of the srm catalog, it is valid and working properly.
    The code was re-entered in a, newly created, version 3.0 catalog-repository.

    Error solved, we upgraded to version 3.0 Support pack 05 patch 2

  • SRM-MDM 3.0 SP10 Patch 1 - logon failed

    Hello there,
    we have a urgend problem after upgrading the SRM-MDM Components and the MDM Server.
    Problem is, that we are not able to logon to the app ui or the search ui. It's not a Problem with the user. When logon to the app ui we receive the message "logon failed".
    Connection to the Repository via MDM Clients works very well. Only the Web UI is not accessable.
    To be sure we are having the right SPs for the Components we downloaded the latest Support Stack that includes all components versions that fits to each other (thats what i think).
    At least we have now
    MDM Server SP06
    MDM Catalog SP10 Patch 1
    Java API SP10 Patch 0
    MDM Connector SP10 Patch 7 (?)
    Here's the information from the connection test via mdm utilities
    !======================================!
    Host-Adresse = 10.199.29.243
    Host Name = mpgmdms
    Repository-Port = 2000
    !======================================!
    MDM-Server-Ports werden geprüft...
    Verbindung ok (Port 59950, Zeit = 0 ms)
    Repository-Ports werden geprüft...
    Verbindung ok (Port 2000, Zeit = 0 ms)
    Verbindung ok (Port 2001, Zeit = 0 ms)
    Verbindung ok (Port 2002, Zeit = 0 ms)
    JAVA-API-Version von MDM ermitteln
    Admin Version = 7.1.07.101
    Build Version = 7.1.07.166
    Content Version = 7.1.07.101
    Meta Version      = 7.1.07.101
    !======================================!
    Verbindung zu MDM-Server 10.199.29.243 wird hergestellt
    MDM-Server-Version wird ermittelt...
    Version = Version 7.1 (7.1.06.234 Win64)
    !======================================!
    Installierte Repositories werden ermittelt...
    -> MPG_DEV_MASTER (S36/ORCL)
    -> MPG_DEV_SLAVE2 (S36/ORCL)
    -> MPG_DEV_SLAVE (S36/ORCL)
    -> MPG_TEST_REPOSITORY (S36/ORCL)
    From the visua administrator we get the following releaseinformation:
    MDM_Connector 1000.710.700.7.1.201105150802
    MDM_JAVA_API 1000.710.0.7.166.20110410110411
    SRM_MDM_CAT 1000.3.0.10.1.20110429065011
    Within the MDM Console we get a some log entries when trying to log in.
    Hope you can help me.
    Thank your
    Rico
    Edited by: Rico Stoll on May 25, 2011 6:31 PM

    ur API / connector and MDS are on diff SP levels :
    JAVA-API-Version von MDM ermitteln
    Admin Version = 7.1.07.101 Interface CRC=0x7d50b0cf
    Build Version = 7.1.07.166
    Content Version = 7.1.07.101 Interface CRC=???
    Meta Version \t= 7.1.07.101 Interface CRC=0x3a0a3732
    !======================================!
    Verbindung zu MDM-Server 10.199.29.243 wird hergestellt
    MDM-Server-Version wird ermittelt...
    Version = Version 7.1 (7.1.06.234 Win64)
    upgrade the MDS to SP 07 and things should start working !
    thanks
    -Adrivit

  • Things to look for in SRM 7.0 upgrade.

    Hello Everyone,
    We are using SRM 5.0 with Extended classic scenario and we need to upgrade from SRM 5.0 to SRM 7.0.
    We are going to send RFP to different vendors for this upgrade project.
    As a project manager what I should ask from different vendors before the upgrade?
    What things I should look for from vendors before the SRM 7.0 upgrade or what questions I should ask to different vendors before the SRM 7.0 upgrade?
    Regards,
    Khushbu.

    Hi Khushbu ,
    This are the sample basic question for SRM upgrade .
    SAP SRM Upgrade Questionnaire
    Basic Information
        Company / Project Name
        Current Backend SAP R/3 or ECC Version / Plug-In Version
            - OLTP Backend System 1
            - OLTP Backend System 2
            - OLTP Backend System 3
            - OLTP Backend System n
        Current SRM Release / Plug-In Version
    Components in SAP SRM
    Please list which of the following Components are currently implemented (Y/N) and their release versions :
    a) EBP
    b) SUS
    c) Live Auction
    d) Requisite Catalog
    e) CCM
    f) MDM Catalog
    f) IPC
    b) XI
    h) Enterprise Portal
    i) BW (SRM Analytics)
    j) ITS
    k) CRM Middleware
    l) HR Integration
    m) Others
    If the answer to any of the above is No, Are you considering implementing additional SRM components?  If so, please list the components
    Do you have any of the following scenarios :
    a) 1 EBP client connected to Multiple backend SAP R/3 clients
    b) Multiple EBP Clients connected to Multiple backend SAP R/3 systems
    SRM Scenarios currently used
    Self Service Procurement
    Service Procurement
    Plan Driven Procurement
    Contract Management
    Supplier Self Services
    Strategic Sourcing - RFx, Live Auction
    Other SAP Solutions
       Please List R/3 or ECC  Modules Currently In Use
    Have you implemented SAP Supply Chain Management (APO)?
    If yes, what is your current APO Version
    Have you implemented Product Lifecycle Management (PLM)?
    If yes, what is your current PLM Version
       Please name any other SAP Add-ons or Industry Solutions in use
    Basis Information
        Database release for current backend SAP R/3 or ECC system
        Operating System release for current backend SAP R/3 or ECC System
        What is your Hardware Platforms for current backend SAP R/3 or ECC system (e.g.HP, IBM, etc.)?
    How many systems are in your landscape for current backend SAP R/3 or ECC system (e.g., Development, Quality Assurance, Production, etc.)?
         How large is your current Production Database in backend SAP R/3 or ECC system (in GB)?
    Current SRM Database Size?
       Database release for Current SRM system?
       What is your SRM Hardware Platforms (e.g., HP, IBM, etc.)?
    What is your current OS for the different components of SRM which are in use
    Please explain the complete system Landscape for SRM (Use a separate sheet, if required)
    SRM Data Conversion or Replication (if any)
       Business Partners
        How many vendor records are handled in SRM ?
    Product Masters
        How many product master records are there in SAP R/3 ?
        How many product master records are available in SRM ?
    Legacy Systems and their Migration
    Any new data migration from legacy systems
    System Enhancements
    Custom Developments
        Complex
        Medium
        Minor
    Custom Tables
    Custom Java codes (e.g in IPC)
    Badi's / User Exits
    Screen modifications
    z-transactions
    Non-SAP External Systems and Integration issues
       Have you integrated any Non-SAP External systems to SRM ? 
       List of Interfaces :
       1) EBP-Business Connector-WOI (IBM Web Order Interface)
       2)
       3)
    Is SRM integrated to a Third Party Tax Engine e.g Vertex, Taxware
         Are you using email servers integrated with SRM ?  If yes, which email system (e.g., Lotus Notes, Outlook, etc.)?
    XI (Exchange Infrastructure)
    List of Interfaces
    1) P.O create
    2) P.O Change
    3) Order Acknowledgement
    4)
    5)
    Project Management Tools used in Project
    Are you using Solution Manager ?
    Other Tools used
    Size of  Current SAP Team and Availability of SAP Resources
          What is the size of the existing SAP SRM support team : Any Consulting / AMS Team
          What is the size of the existing SAP SRM support team : Internal Team / COE
    Training Requirements
        Please Explain the User training methods used in Previous ERP or SRM implementations.
        How many Super Users, and End Users got trained during SRM 3.0 implementation?
       Do you have additional training Requirements?  If so, please describe.
       What testing tools are used currently ?
    Project Constraints
    What are the budgetary constraints for this project?
    What are the  resource constraints for this project?
    What are the timeline (duration) constraints for this project?
    Additional Comments
    Is there any plan to upgrade any of the OLTP R/3 systems in the near future
    UNICODE
    Are your current OLTP R/3 systems Unicode complaint
    Is your current SRM system Unicode Compliant
    What languages are used in the current R/3 systems
    What additional languages are required in the R/3 systems
    What languages are used in the current EBP system (Core)
    What additional languages are required in the EBP system (Core)
    What are the languages supported in the HTML layer currently
    What additional languages are required in the HTML layer
    Hope this will be useful to you .
    Thanks & Regards
    Pradeep Kumar Dondeti

  • Need SMP link for SRM MDM GUI setup

    Hello all,
    Can any one help me by providing the link for the following downloads in SMP.?
    -- SRM MDM Console
    -- SRM MDM Import Manager
    -- SRM MDM Workflow
    Thanks,
    Dinesh.

    Dinesh -
    Procurement Catalog Management based on SAP NetWeaver Master Data Management allows you to create, cleanse and manage your centralized supplier catalog facilitating a smooth flow in the procurement process. 
    SAP NetWeaver Master Data Management technology ensures data integrity and enables the content management processes in SRM-MDM Catalog. It lets you manage data and communication in an integrated environment for streamlined catalog content management.
    first of all you can get all relevant materials for SAP MDM latest in below link
    https://websmp203.sap-ag.de/installmdm71/
    for console, IM, DM and syndicator as well.
    for SRM MDM perspective follow
    SAP MDM Procurement Catalog Management
    in this you can also get wiki for SRM MDM solution.
    HTH
    thx
    Deep

  • SAP SRM-MDM

    Hello
    We have read installation guide "SAP Netweaver MDM 5.5 SP05", page 22, we want install MDM Connector and MDM Java API, in "installation procedure", it is indicate
    1. Extract the files from the archives.
    The javadoc folders contain an HTMLbased
    collection of documents that
    describe the Java API. Make sure you
    retain the directory structure.
    2. Deploy the SDA files on Web AS
    Java using the Software Deployment
    Manager (SDM). MDM Connector uses
    the mdm4j library as a shared library to
    support generic connection.
    3. Store the JAR files at the standard
    location for the application that uses
    them.
    4. Include the path to the JAR files in
    the class path for the application that
    uses them. This may be an
    environment variable, a command line
    argument, or an application
    configuration parameter.
    Only we are clear point 2, but rest, we are not sure, please could you clear us it ???
    Thanks

    Hello :
    Thanks for your help...
    We have trying configure SRM-MDM Catalog, we have installed "matrix aplication" ( deploying MAtrixServer_1.0.EAR and MatrixApp_1.0.EAR in WAS 6.40) and MDMConector (MDMJavaAPI) ( deploying MDMJAVAAPI<>.sca in WAS 6.40). We want connect to repository with "Matrix Aplication" but we don´t have clear, point 3 and 4. We don´t use "developer studio"
    3. Store the JAR files at the standard
    location for the application that uses
    them.
    4. Include the path to the JAR files in
    the class path for the application that
    uses them. This may be an
    environment variable, a command line
    argument, or an application
    configuration parameter.
    We use this url connect to repository from "Matrix Aplication"
    http://poseidon:50200/webdynpro/dispatcher/local/MDMMatrixApp/MatrixApp?user=mdmuser&server=SOCRATES&port=2345&repository=MDM&lang=US&x=0
    Thanks and best regards

Maybe you are looking for