1. WebServices Installation Guide
  2. Deploy Application Interface WebServices
  3. Deploy Webservices

2.4 Deploy Webservices

The following section details the steps to be followed for the deployment of WebServices in Enterprise Manager.

Parent topic: Deploy Application Interface WebServices

2.4.1 Deploying WebServices in Enterprise Manager

  1. Download and unzip the WebServices - ofsllxws.zip.
  2. Following is a mapping of which EAR is needed for which service:

    Table 2-3 Mapping of EAR

    dbkls-xxws.ws.app-dt.ear dbkls-xxws.ws.app-ds.ear dbkls-xxws.ws.app-ro.ear
    DT Interface: To receive loan application from dealer track DS Interface: To receive edocs application update RO Interface: To receive loan application from route one
    DT Interface: To receive loan application/deal update from dealer track DS Interface: To receive edocs com­ment update RO Interface: To receive loan application/deal refresh from route one
    DT Interface: To receive com­ments from dealer track DS Interface: To receive edocs loca­tion update RO Interface: To receive com­ments from route one
    LOSPostStatusRequestSer­vice: To post comments to dealer track   LOSPostStatusRequestSer­vice: To post comments to route one
    LOSPostStatusRequestSer­vice: To post application sta­tus to dealer track   LOSPostStatusRequestSer­vice: To post application status to route one
    ILOSPostDealerDetailsSer­vice: To post dealer details to dealer track   ILOSPostDealerDetailsSer­vice: To post dealer details to dealer track
        LOSEContractService: To recieve contract information from RouteOne
  3. Unzip all the ear files present:
    • dbkls-xxws.ws.app-dt.ear
    • dbkls-xxws.ws.app-ro.ear
    • dbkls-xxws.ws.app-ds.ear
  4. Open each of the unzipped files and unzip the war file.

    Figure 2-21 Deployment in EnterpriseManager 1


    Description of Figure 2-21 follows
    Description of "Figure 2-21 Deployment in EnterpriseManager 1"

  5. It creates a WEB-INF file.

    Figure 2-22 Deployment in EnterpriseManager 2


    Description of Figure 2-22 follows
    Description of "Figure 2-22 Deployment in EnterpriseManager 2"

    After unzipping the war file to directory, the directory will have the following structure.

    • / dbkls-xxws.ws.app-ds / dbkls-xxws.ws.app-dt / dbklsxxws.ws.app-ro

      WEB-INF (directory)

      ---->classes (directory)

      - config

      - class files (in package folders)

      -----> lib (directory)

      - OfsllCommonCSF.jar

      ------> wsdl (directory)

      - *.wsdl

      -----> *-java-wsdl-mapping.xml

      -----> web.xml

      -----> weblogic.xml

      -----> weblogic-webservices.xml

      -----> weblogic-webservices-policy.xml

      -----> webservices.xml

  6. To edit the web interface config files, navigate to the above WEB-INF > classes > config. Edit the following configuration files with the application url and port.

    For complete details on configuration parameters, refer to Configuration parameterssection in Appendix chapter.

  7. Login to Web Logic application server enterprise manager (e.g.:http://hostname:port/em).

    Figure 2-26 Deployment in EnterpriseManager 6


    Description of Figure 2-26 follows
    Description of "Figure 2-26 Deployment in EnterpriseManager 6"

  8. Enter valid login credentials.
    The following window is displayed.

    Figure 2-27 Deployment in EnterpriseManager 7


    Description of Figure 2-27 follows
    Description of "Figure 2-27 Deployment in EnterpriseManager 7"

  9. Expand the weblogic domain present in the left pane.
    The following window is displayed.

    Figure 2-28 Deployment in EnterpriseManager 8


    Description of Figure 2-28 follows
    Description of "Figure 2-28 Deployment in EnterpriseManager 8"

  10. Right click on WS_ManagedServer in left panel, select Application Deployment > Deploy.

    Figure 2-29 Deployment in EnterpriseManager 9


    Description of Figure 2-29 follows
    Description of "Figure 2-29 Deployment in EnterpriseManager 9"

  11. The following window is displayed.

    Figure 2-30 Deployment in EnterpriseManager 10


    Description of Figure 2-30 follows
    Description of "Figure 2-30 Deployment in EnterpriseManager 10"

  12. Browse to the folder containing the WebService. Eg:
    /ws-as/ofsllxws/dbkls-xxws.ws.app
    Click Next.

    Figure 2-31 Deployment in EnterpriseManager 11


    Description of Figure 2-31 follows
    Description of "Figure 2-31 Deployment in EnterpriseManager 11"

  13. The following window is displayed. Select the server on which the WebService needs to be deployed. Click Next.

    Figure 2-32 Deployment in EnterpriseManager 12


    Description of Figure 2-32 follows
    Description of "Figure 2-32 Deployment in EnterpriseManager 12"

  14. The following window is displayed. Check the context root and select the Distribution option as Install and start application (servicing all requests). Click Next.

    Figure 2-33 Deployment in EnterpriseManager 13


    Description of Figure 2-33 follows
    Description of "Figure 2-33 Deployment in EnterpriseManager 13"

  15. The following window is displayed. Click Deploy.

    Figure 2-34 Deployment in EnterpriseManager 14


    Description of Figure 2-34 follows
    Description of "Figure 2-34 Deployment in EnterpriseManager 14"

  16. The following window is displayed. Click Close.

    Figure 2-35 Deployment in EnterpriseManager 15


    Description of Figure 2-35 follows
    Description of "Figure 2-35 Deployment in EnterpriseManager 15"

  17. If required, similarly deploy rest of the WebServices.
  18. In case the context root has to be changed for the WebServices, it can be changed by editing the application.xml or through the console. To change through console, login to WebLogic Server 12c console (http://hostname:port/console).
  19. Go to Deployments > <select the service deployment> > Configuration General and modify the context root to the recommended name as follows:

    Table 2-4 Service EAR

    Service Service EAR Recommended Context Remark
    Edocs Interface dbkls-xxws.ws.app-ds.ear dbkls-xws-app-ds If this the recommended context name is not used, then the Service URLs in the configuration files needs to be changed
    Dealer Track Interface dbkls-xxws.ws.app-ds.ear dbkls-xws-app-dt If this the recommended context name is not used, then the Service URLs in the configuration files needs to be changed
    Route One Inter­face dbkls-xxws.ws.app-ro.ear dbkls-xws-app-ro If this the recommended context name is not used, then the Service URLs in the configuration files needs to be changed
  20. Ensure that the application status is Active.

Parent topic: Deploy Webservices