it is assumed that a managed server is already created for the following web service deployment(s) as per the process detailed in Application Installation guide section - 3.2 Creating Domain and Servers.
Similarly follow the above steps to create the following data sources:
It is not recommended to run OFSLL WebServices with the test certificates in production. You have to get:
For more details on keytool refer the link: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html
SSL debugging can be enabled by adding the following to managed server start-up script: ‘Dssl.debug=true’
For WLS 12c by default (acting as a client) will send sslv2 hello for the SSL handshake to TLS service. The TLS service will not respond to SSLv2 hello and the connection will be dropped.
The fix for the problem is to set Dweblogic.security.SSL.protocolVersion=TLS1 at the Managed server level in which the WebServices have been deployed.
In order Configure RouteOne, you need to create credentials and system policies.
Similarly you need to create the following Maps and corresponding keys as indicated in following table.
Maps |
Key Name |
Username |
Password |
Description |
ofsll.int.routeone |
routeone_key_store_pd |
keystorePassword |
changeit |
The keystore password |
routeone_key_alias |
roKeyAlias |
routeone_pub_tst |
RouteOne's public key alias name.The public key is needed to verify the xml signature of the request. |
|
routeone_sscro_key_pd |
sscroKeyAlias |
ssc_routeone |
OFSLL's private key alias name. The private key is used to sign xml response to RouteOne |
|
routeone_sscro_key_passsword |
sscroKeyPassword |
demotestSSCR1 |
OFSLL's private key password |
You need to provide access permission for the below mapping. For details on how to set the access permission, refer to point 9 in ‘Create Credentials and System Policies’ topic available in Application Installation Guide.
Permission Class |
Resource Name |
Permission Actions |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName= ofsll.int.routeone,keyName=* |
read |
dbkls-xxws.ws.app.ear |
dbkls-xxws.ws.app-dt.ear |
dbkls-xxws.ws.app-ds.ear |
dbkls-xxws.ws.app-ro.ear |
DialerIntegrator: Service to integrate with third party dialer systems |
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 |
CSSAccountDetailsRequestService: Service to fetch Account Details by account number |
DT Interface: To receive loan application/deal update from dealer track |
DS Interface: To receive edocs comment update |
RO Interface: To receive loan application/deal refresh from route one |
CSSAccountSearchRequestService: Service to fetch Account Details by attributes such as AccountNumber, CustomerFirstName, CustomerLastName, SSN |
DT Interface: To receive comments from dealer track |
DS Interface: To receive edocs location update |
RO Interface: To receive comments from route one |
CSSPostTransactionsRequestService: To post different transactions such as update address, update phone number, update ACH details, etc |
LOSPostStatusRequestService: To post comments to dealer track |
|
LOSPostStatusRequestService: To post comments to route one |
CSSAccountPayOffQuoteRequestService: To get the account payoff quote |
LOSPostStatusRequestService: To post application status to dealer track |
|
LOSPostStatusRequestService: To post application status to route one |
LOSeApplicationRequestService:Edocs application update service |
ILOSPostDealerDetailsService: To post dealer details to dealer track |
|
ILOSPostDealerDetailsService: To post dealer details to dealer track |
LOSApplicationRequestService: Loan application entry service |
|
|
|
LOSApplicationSearchRequestService: Application Search service |
|
|
|
LOSApplicationSearchRequestService: Application Search service |
|
|
|
LOSApplicationCommentUpdateService: Edocs application comment update service |
|
|
|
LOSPostStatusRequestService: Service to post loan application status |
|
|
|
LOSApplicationUpdateService: Service to update an existing application |
|
|
|
LOSCheckStatusRequestService: Service to check application status |
|
|
|
LOSApplicationAccountWebService: Service to create Account number in OFSLL |
|
|
|
|
|
|
LOSEContractService: To recieve contract information from RouteOne |
After unzipping the war file to directory, the directory will have the following structure
WEB-INF (directory)
---->classes (directory)
- config
- class files (in package folders)
-----> lib (directory)
- jdom-2.0.6.jar
- OfsllCommonCSF.jar
- soap-2.3.1.jar
------> wsdl (directory)
- *.wsdl
-----> *-java-wsdl-mapping.xml
-----> web.xml
-----> weblogic.xml
-----> weblogic-webservices.xml
-----> weblogic-webservices-policy.xml
-----> webservices.xml
For complete details on configuration parameters, refer to “Configuration parameters” section in Appendix chapter.
Eg: /ws-as/ofsllxws/dbkls-xxws.ws.app
Click ‘Next’.
Service |
Service EAR |
Recommended Context |
Remark |
Webservices |
dbkls-xxws.ws.app.ear |
dbkls-xws-app |
If this the recommended context name is not used, then the Service URLs in the configuration files needs to be changed |
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 Interface |
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 |