Show TOC

Migrating J2EE Library DC to Enterprise Application DCLocate this document in the navigation structure

Context

Use this procedure to migrate a Start of the navigation path J2EE Server Component Next navigation step Library  End of the navigation path DC project created on SAP NetWeaver 7.0 to an Enterprise Application DC in SAP NetWeaver 7.1 CE.

Note

There is limited support on already existing old DC projects of this type. You can import, build and deploy them using the SAP NetWeaver Developer Studio, but you cannot create new J2EE Library DCs. We recommend that you migrate the J2EE Library DCs to Enterprise Application DCs.

Prerequisite

You work in the Development Infrastructure perspective.

You have a Library DC project created on SAP NetWeaver 7.0 that you want to migrate to an Enterprise Application DC in SAP NetWeaver 7.1 CE.

Procedure


  1. If the Start of the navigation path J2EE Server Component Next navigation step Library DC End of the navigation path project is not a local project, import it from the Design Time Repository (DTR) into an existing Library DC Project in the Developer Studio. If the project is local the Library DC project will be imported after the old workspace is opened with the Composition Environment Developer Studio.

  2. Create an initially empty Enterprise Application DC project.

    From the menu path choose Start of the navigation path New  Next navigation step Development Component End of the navigation path. Choose Start of the navigation path J2EE Next navigation step Enterprise Application  End of the navigation path as DC type.

  3. Open the Component Properties view and select the newly created project.

    From the menu path choose Start of the navigation path Window Next navigation step Show View  Next navigation step  Other... End of the navigation path. Choose Development Start of the navigation path Infrastructure Next navigation step Component Properties End of the navigation path.

  4. Add references from Enterprise Application DC to the assembly public parts of the Java DCs and External Library DCs that were referred by the Library DC so far.

  5. In case the Library DC has some Java content move that content to a Java DC and make sure that all the build time references are redirected to it. Also adjust the references in the Enterprise Application DC Project.

  6. Redirect the runtime references of all the library clients to the new Enterprise Application DC.

Results

In the DTR was configured the System Landscape Directory (SLD) to use. The Java DC is called a1s~utiltest and is referred by an old Library DC called a1s.libtest.

The EAR DC is called a1s.eartest , referring the Library DC. The EAR DC also contains a Web DC a1s~webtest , which uses the Util Java DC.

  1. Import from DTR the EAR, Web, Java and Library DCs in the workspace.

  2. Check that the Library DC project is marked with an error marker stating that migration is required.

  3. Create new EAR 1.5 DC project test_lib_ear .

  4. Create a used DC dependency from the test_lib_ear DC to the public part of the java DC.

  5. From you Web module webtest where the libraries are used you should:

    1. Add the library JARs to the class path of the webtest project using SetAdditionalLibraries menu - choose the library EAR.

    2. Add a Build Time DC dependency to the library JARs from the External Library DC project, to allow the DC build to compile them.

  6. Build, deploy and run the application.

  7. Check that the JSP is executed normally.