Saving and Restoring Objects and Projects

Access JD Edwards EnterpriseOne OMW.

  1. In JD Edwards EnterpriseOne OMW, select the object or project that you want to save.

  2. Click the Save button in the center column.

    The jdeomw dialog box displays. OMW provides two methods with which to save an object. The first method is to save the object to a zip file. If you save the object to a zip file, OMW saves the object or project as a local copy in a format compatible with Zip, Jar and JDEdwards Change Assistant technologies.The second method is to save the object to a shared database location. The shared location is configured by your OMW administrator, and is the most common method with which you will save objects or projects.

  3. Click Yes to save the object to a zip file, or click No to save the object to a pathcode save location.

  4. If you clicked Yes, continue to step 5. If you clicked No, OMW saves the object to pathcode save location.

  5. On the Select Folder form, select the folder to which you want to save the object, and then click Open.

To restore an object or project, access JD Edwards EnterpriseOne OMW.

  1. In JD Edwards EnterpriseOne OMW, select the object or project that you want to restore.

  2. Click the Restore button in the center column.

    The jdeomw dialog box displays and provides options for you to choose from where you want to restore the object. You can choose to restore the object from a zip file, or to restore the object from the Save location specified by the OMW administrator.

  3. Click Yes to restore the object from a zip file, or click No to restore the object from a pathcode save location.

  4. If you clicked Yes, continue to step 6. If you clicked No, OMW restores the object from the pathcode save location.

  5. On the Select Folder form, select the PAR file from which you want to restore the object or project, and then click Open.

    OMW restores the object or project.

Note: The E1Local database is removed in Tools Release 9.2.5. When a Restore is performed, the user spec tables will be updated with records for the signed-in user. These records will be used when in design and at runtime.