Home

SoftRater User Manual - Oracle Documentation

Contents

1. Notes RJ Refresh B to Group Name Type Last Updated Enable Default D V Output Separate Output Code RG Call AU BP Output Group Jun 18 2014 6 15PM V V 48A1714561 RG_Call_AU_BP_2 Output Group Jun 24 2014 1 39PM v FC42721399 Figure 1 Output Code In order for you to be able to use a result group it must have been Enabled when the package was created see the RateManager topic Editing Result Group Options lt c gt Node Category The lt c gt category node marks the beginning of input data for a specific category of information i e home car driver policy etc It has the following attributes i identifier Zero always indicates Policy level inputs other categories are user definable Required desc description of category Optional Example lt c i 0 desc Policy gt The Policy category is always a direct child of the lt rate gt node except for overrides in the lt program gt node described later It is also the top level category node The Policy category node typically has an ID of zero i e i 0 Item level categories are nested under the Policy category node Example c i 0 desc Policy gt m i 1212 nz Eff Date v gt m i 1214 nz PrimInsuredAge v gt m i 1215 nz SeclnsuredAge v gt lt c i 5 desc Home gt lt c i 7 desc Scheduled Property gt ze lc c iz 5 desc Home gt lc lc
2. Will produce this result XML lt ibdoc gt lt result gt lt result gt lt result gt lt result gt lt ibdoc gt The root node is not returned in the result XML automatically It must be specified in the call using the AddRoot attribute NOTE Results may not be returned in the order in which they were submitted To assure that results are returned in the same order as entered verify the Web Service Rating Thread entry on the SoftRater Engine page of the Insbridge Framework Administrator IBFA An entry of 1 will return results in the same order An entry greater than the number of rates submitted will return results in order If you know that you will always have three rates per request you can set the threads to 3 or greater Be aware that a higher thread count may affect performance The default setting is 2 Multiple lt program gt nodes This request XML lt ibdoc gt lt rate gt lt heading gt lt program gt lt program gt lt program gt lt program gt lt heading gt lt C gt lt C gt lt rate gt 33 Chapter 6 Insbridge XML Windows Example lt ibdoc gt Will produce this result XML lt ibdoc gt lt result gt lt program gt lt C gt lt C gt lt program gt lt program gt lt C gt lt C gt lt program gt lt result gt lt ibdoc gt 34 Chapter 6 Insbridge XML Windows Example Multi State Request To rate against mul
3. m Node Map The m map node represents an individual attribute value pair mapped for a specific SoftRater Package hosted by SoftRater In the input case it identifies an input attribute recognized by the SoftRater 22 Chapter 6 Insbridge XML Windows Example Package or Packages listed in the lt heading gt node and its associated value The lt m gt node s attributes are i input identifier Required n name description of input Optional V value of input Required The m node is always a child of a c category node and is an attribute value pair for that specific category instance see the Policy category example 23 Chapter 6 Insbridge XML Windows Example INSBRIDGE XML RESULT FORMAT The following is an example of an Insbridge rate request result XML document The result XML is very similar to the input XML format lt result lob 2 st 6 gen_date 2 19 2014 1 55 32 PM gt lt program parent_id 1 program_id 318 program_ver 1 status PASS gt c i 5 gt lt m i Dwelling_1 v 640 gt m i Dwelling_3 v 0 gt m i Dwelling_5 v 0 gt m i replec v 0 gt lt m i COV Replacement Cost Contents v 0 gt lt m i COV Mortgage Payment v 0 gt lt m i Dwelling_10 v 0 gt m i Dwelling_11 v 34 gt lt m i COV Replacement Cost Dwelling v 0 gt m i Dwelling_13 v 0 gt lt m i Dwelling_13 v 674 gt lt m i COV Busin
4. Parent or Insbridge Company parent_id Identifier available by default program_id Selected Program Identifier available by default Selected Program Version program ver Identifier available by default region format Locale used by program available by default result def Output group used available by default result def name Output group name used status Pass Fail status available by default Example base worksheet gen type 0 package date 2014 08 11T04 42 13 parent id 8659 program id 21 program verz 1 region format en US result def2 C7A5730473 result def namez Group 1 status PASS algorithm Node A subset of the Worksheet node This node identifies the algorithm being run Name of the category where the category name algorithm was created available by default item Category ID available by default name Algorithm name available by default Type of algorithm rating type underwriting or driver available by default Example algorithm categoryName Policy item 1 name AG Algorithm 1 type Rating step Node A subset of the algorithm node This node identifies the step type and step number used in the algorithm stepName assignment The type of step being executed available by default stepNumber Example step stepName arithmetic stepNumber 1 gt term Node A subset of the step node
5. WHEN IS INFORMATION REMOVED FROM THE CACHE Information is removed from the cache only in the following cases e Caching is disabled on the SoftRater Engine Configuration screen in the Insbridge Framework Administrator and the change is saved by clicking SAVE In this case all information is removed from the cache for all programs e Anew package is loaded to an environment for a program that is currently cached In this case all information is removed only for that specific program and that specific environment e When a package is loaded into a cluster environment the cache is cleared for all environments in the cluster This prevents any environment from having outdated packages in cache e An update is made to a subscriber s SoftRater Explorer configuration settings i e an environment is added deleted or edited a virtual file server is added etc In this case all information is removed from the cache for all programs e The server is restarted or shutdown NOTE Cache equals true even when the cached program is manually removed from IBFA As long as cache is on the Insbridge Engine will use the cache that the current rate request enters itself or from other requests CACHE USE EXCEPTION There is an occasion when SoftRater will not use the cache when rating e The environment being rated against has a Catalog Type of RateManager The RateManager environment is the location that all local packages are loaded to upon cre
6. lt c gt Node Category The lt c gt category node marks the beginning of input data for a specific category of information i e home car driver policy etc It has the following attributes i identifier Zero always indicates Policy level inputs other categories are user definable Required desc description of category Optional Example lt c i 0 desc Policy gt The Policy category is always a direct child of the lt rate gt node except for overrides in the lt program gt node described later It is also the top level category node The Policy category node typically has an ID of zero i e i 0 Item level categories are nested under the Policy category node Example lt c i 0 desc Policy gt m i 1212 nz Eff Date v gt m i 1214 nz PrimInsuredAge v gt m i 1215 nz SeclnsuredAge v gt lt c i 5 desc Home gt c i 7 desc Scheduled Property gt lc lc 48 Chapter 10 Insbridge XML Java Example c i 5 desc Home gt lt c gt lt c gt m Node Map The lt m gt map node represents an individual attribute value pair mapped for a specific SoftRater Package hosted by SoftRater In the input case it identifies an input attribute recognized by the SoftRater Package or Packages listed in the heading node and its associated value The m node s attributes are defined as follows i input identifier Required
7. Application level services allow administrators to manage nodes from one location rather than navigating to the individual nodes to manage services Application level services include e IBSS Connector Service e Message Processing e Insbridge Task Manager 60 Chapter 11 IBSS Functionality in Java INSBRIDGE CONNECTOR SERVICE The Insbridge Connector Service is a Database Queue and JMS Listener that routes all batched messages to a java class process for execution There are dedicated Start and Stop buttons on the Services page for the Insbridge Connector Service as well as a Properties button to manage Insbridge Connector Service settings Starting the Insbridge Connector Service at the application level starts the service across all nodes configured in a clustered environment If a node should not participate in rating that individual node can be stopped without affecting other nodes by entering the selected node and stopping the service at the node level sa E i ES mn eo B nttp 10101001107001 IESS p ae ls SoftRater Server WEBLOGL X A File Edit View Favorites Tools Help ORACLE Insurance Insbridge SoftRater Server WebLogic 04 08 00 E Ea 1855 Insbridge Connector Service Start Stop Properties The Insbridge Connector Service is a Database Queue and JMS Listener that will route all batched messages to a java dass process for B Config execution Please note these processes may take
8. final boolean aAddResultDesc final boolean aAddResultThatAreEmpty Chapter 7 SofiRater Integration for Java final boolean aDoDebugOutput final boolean aDisableCache final String aTargetEnvironment final int aLOB final int aCompanyld final int aProgramld final float aProgramVersion final int aUseResultEncoding final String aUseResultDefinition final short alnputMappingType final String alnputMappingldentifier final short aOutputMappingType final String aOutputMappingldentifier final boolean aOutputMappingStateFul final String aOutputErrorXpathLoc throws EJBException public String ProcessRequestCustom final String aXMLInput final String aXMLInputTag final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean aAddWorksheet final int aDoDebugOutput final boolean aDisableCache final String aTargetEnvironment final int aLOB final int aCompanyld final int aProgramld final float aProgramVersion final int aUseResultEncoding final String aUseResultDefinition final short alnputMappingType final String alnputMappingldentifier final short aOutputMappingType final String aOutputMappingldentifier final boolean aOutputMappingStateFul final String aOutputErrorXpathLoc final boolean aAddinputsToDb final boolean aAddResultsToDb throws EJBException public String ProcessRequestCustomFromDisk fi
9. lt heading gt lt c i 0 desc Policy gt m i 7 nz PaymentPlanCd v Prepaid gt lt c i 1 desc Location gt lt m i 3 n LocationStateCd v AL gt lt m i 4 n SignsLimit v 2500 gt lt m i 6 n FullCoverageYN v N gt lc lc lt rate gt 29 Chapter 6 Insbridge XML Windows Example Example 1B using input overrides RATE REQUEST lt rate lob 125 gt lt heading gt program parent_id 1002 program_id 1 program_ver 1 custom_id 3PAY gt lt c i 0 desc Policy gt m i 7 nz PaymentPlanCd v 3pay gt lc lt program gt program parent_id 1002 program_id 1 program_ver 1 custom_id 6PAY gt lt c i 0 desc Policy gt m i 7 nz PaymentPlanCd v 6pay gt lt c gt lt program gt program parent_id 1002 program_id 1 program_ver 1 custom_id 9PAY gt lt c i 0 desc Policy gt m iz 7 nz PaymentPlanCd vz 9pay lc lt program gt program parent_id 1002 program_id 1 program_ver 1 custom_id BASE gt lt heading gt lt c i 0 desc Policy gt m iz 7 nz PaymentPlanCd vz Prepaid c i 1 desc Location gt m i 3 n LocationStateCd v AL gt m i 4 n SignsLimit v 2500 gt lt m i 6 n FullCoverageYN v N gt lc lc lt rate gt RATE RESPONSE lt result lob 125 env_def rm gen_date 2014 05 21 11 30 05 AM ibdoc_version 3 1 engine_type windows site_location MACHINE X
10. lt rate gt node signifies which line of business will be rated against This rate request XML lt ibdoc gt lt rate lob 1 gt lt rate gt lt rate lob 2 gt lt rate gt lt ibdoc gt Will produce this result XML Results for Auto lt ibdoc gt result lob 1 gen date 2 9 2014 1 50 31 PM lt result gt result lob 2 gen_date 2 9 2014 1 50 45 PM gt lt result gt lt ibdoc gt Wee Results for Home 35 Chapter 7 SOFTWARE INTEGRATION FOR JAVA SoftRater is an EJB component hosted in the Application Server and accessible through the following software integration methods Each Application Server has a default port that is used NOTE WebLogic Port 7001 WebSphere Port 9080 JBoss Port 8080 Port numbers change depending on your Application Server These defaults are current as of this release When rating custom XML the engine has the option of stateful rating The SoftRater WSI adds the contents of the rating results to the document that was submitted for rating This is an important consideration when constructing XSLT mapping files Software Integration Methods 36 HTTP SOAP Proxy SoftRater Web Service The WSDL location of all deployed web services is provided in the IBSS application The WSDL URL of SoftRater SoftServices SoftData and Batch Connector Webservices are provided on the Node Information Page for the node you want t
11. lt result gt node marks the beginning of a rate request result There is a one to one correspondence between lt rate gt nodes in the request XML to lt result gt nodes in the response XML The result node attributes are defined as follows 50 Line of business indicator corresponding to the lt rate gt request nodes lob attribute PolicyNumber The unique identifier generated in the rate request Used to distinguish different requests env_def Environment definition holds the value for the database environment to which the request and result information are mapped gen_date Server creation timestamp indicating when this response was created ibdoc_version The insbridge document version number Chapter 10 Insbridge XML Java Example engine_type Engine type is the name of the application server in which the application is deployed site_instance Site Instance is the name of the Node in IBSS which processed the particular rate request db rt INPUT BATCH ID Database runtime input batch identifier is the batch id generated by the engine while submitting a request This id is used in getting the Input xml and to delete input batch db rt INPUT FILE ID Database runtime input file identifier gets generated while submitting a rate request db rt RESULT BATCH ID Database runtime result batch id is the unique id The tracking attributes on the rate node are returned in the result XML document as attributes in the result
12. n name description of input Optional V value of input Required The m node is always a child of a c category node and is an attribute value pair for that specific category instance INSBRIDGE XML RESULT FORMAT The following is an example of an Insbridge rate request result XML document The result XML is very similar to the input XML format result lob 2 PolicyNumberz XMLInput ChangeAutoComplex 127 em defZ ORACLE DR gen date 2014 05 20 01 02 45 PM ibdoc versionz 3 1 engine typez weblogic site location2 site instance LOCAL db rt INPUT BATCH ID 2 do rt INPUT FILE ID2 10 db rt RESULT BATCH ID 16 program parent idz 1 program idz 318 program verz 1 package date 2013 09 04T13 12 38 status PASS gen type 1 region format en US db rt OWNER INFO ID 2 1i db rt DB REF DATA ID 1 db rt RESULT REF DAT ID VAR 2 4 db rt RESULT FILE ID 16 db rt RESULT PROGRAM ID VAR z 16 from cache true lt c i 5 gt m iz Dwelling 1 v 640 gt m iz Dwelling 3 v 0 gt m iz Dwelling 5 v 0 gt m i replec v 0 gt lt m i COV Replacement Cost Contents v 0 gt lt m i COV Mortgage Payment v 0 gt lt m i Dwelling_10 v 0 gt lt m i Dwelling_11 v 34 gt lt m i COV Replacement Cost Dwelling v 0 gt lt m i Dwelling_13 v 0 gt lt m i Dwelling_13 v 674 gt lt m i COV Business Pursuits v 0 gt m i COV Permitted Incidental Occupancies v 0 gt l
13. 1095 nz Wood Tile SlateRoofType v gt m i 1096 nz HomeDeductible v gt m i 1098 n WindstormOrHailDeductible v gt m i 1100 n2 CentralStationFireAlarmInd v gt m i 1101 nz CentralStationBurglarAlarmlInd v gt lt c i 8 desc Coverage gt m i 1204 n CovCd v gt m i 1205 n Cov Limit v gt m i 1207 n CovEff_ Date v gt lt c gt c i 9 desc Endorsement gt m i 1181 n EndorCd v gt m i 1182 nz EndorRatelnd v gt m i 1190 n EndorEff_Date v gt m i 1191 n Parm5 v gt Chapter 6 Insbridge XML Windows Example lt c gt lt c gt lt c gt lt rate gt lt rate gt Node The lt rate gt node marks the beginning of a rate request for a specific line of business This node has the required attribute lob which identifies the line of business for the request In the following example the lob attribute is set to 2 which represents Home insurance according to the Insbridge standard line of business mappings see RateManager Admin User Guide The rate node attributes are defined as follows lob Line of business indicator per Insbridge standard lob codes Required env_def Rating environment indicator per Insbridge Framework Administrator Optional Allows the user to override the default rating environment By default SoftRater rates against the default environment as set up in the Insbridge Fra
14. Interface 12 company nm Index Attributes 25 31 32 51 54 55 Custom Message 15 Custom ml Submitting 13 D d Attribute 26 52 Data Handling Out of System 16 41 db rt INPUT BATCH ID Attributes 51 db rt INPUT FILE ID Attributes 51 do rt RESULT BATCH ID Attributes 51 Debug Module Tracing 67 Debug Output 16 Options 41 Defining Cache Hit 9 Cache Miss 10 Definition SoftRater v Delete Input XML from Disk Options 41 desc Attribute 22 48 Direct JNDI interfacing 36 Disable Cache Options 41 Disabled Cache 11 Double Quote Invalid Characters 46 E Edition Notice 2 EJB Component WebSphere 36 EJB Interfaces 36 Enabled Result Group 22 48 engine type Attributes 51 env def Attributes 20 50 Environment Web Service Interface 12 EnvRef 16 Error Logs 69 Error Node Created at Root Level 18 43 ESI Overview 69 Example CH 14 15 Cache Hit 10 Cache Miss 10 Category Node 22 26 48 52 Category Node Nested 22 26 48 52 env def Override Default 20 46 Heading Node 20 47 Input Node 26 53 Input Overrides 53 Insbridge Rate Request Result XML Document 24 49 Interface 37 Javascript 14 Multiple rate Nodes 33 57 Multiple Line of Business Request 35 59 Multiple Program Nodes 33 58 Multiple Rate Request 33 57 Multiple State Request 35 58 Program Node 25 31 51 54 Program Node w Heading Option Request 25 51 program id 21 47 Rate N
15. JMS Response messages can be viewed through the Message Process option in IBSS You can view or get the status of the request cancel the request before the engine picks it up for processing abort a request that is processing and purge the completed failed cancelled aborted requests The action you can take depends on the status selected After the status is selected the action button is updated with the corresponding action Status Dropdown Button Action Completed Purge Failed Cancelled Aborted Available statuses of a request after submitting to the engine Pending A request is first submitted to the engine with the status pending This means that the engine has not picked up this request for processing Processing As soon as the engine picks up the request from the table the status changes to processing Completed After the engine has successfully processed a rate request the status of the request changes to completed Failed If any error is encountered while processing the request the status changes to failed Details of the exception can be found in the corresponding logs Cancelled After a request is submitted you can cancel the request before it is picked up by the engine Cancelled requests will not be picked up by the engine for processing The request has to be submitted again in order to be processed Aborted Requests cannot be cancelled after being picked up by the engine If the request i
16. This node identifies the values being used at the time of execution termType 54 The step number in the algorithm available by default The type of term being used available by default Chapter 10 Insbridge XML Java Example Variable operator and so on The name or type of the variable Only if value returned Constants valueNam SES operator and so on being used do not have a value returned Current value at this point in the Only if value returned operators execution do not have a value returned Example term termType inputVariable valueName Date1 2014 01 02 lt term gt Time Statistics Time tracking statistics can be included if enabled on the Insbridge Framework Administrator SoftRater Engine page The following node segment will be included in the Insbridge Response XML document returned from the engine Example lt stats gt lt start_time gt 02 06 2014 04 25 35 0280 PM lt start_time gt lt stop_time gt 02 06 2014 04 25 35 0316 PM lt stop_time gt lt running_time gt 36 lt running_time gt lt stats gt lt start_time gt The start time is the internal system tracking time from the just before the SoftRaterEJB engine starts any processing parsing or any manipulation of the Insbridge XML Request but after the XML payload has been marshaled from the integrate client to the SoftRaterEJB system lt stop_time gt The stop time is the internal system tracki
17. by the engine Information logs can be helpful in debugging when there is some exception in the execution process But as the IBSS application logs provide all the steps involved in any process enabling information logs may be unnecessary The amount of logs returned may be more information than is needed In order to avoid this situation the option to enable disable information log tracing is available The information log tracing can be enabled only when there is an exception or for audit purposes In addition a particular module can be traced using the Debug Module Tracing option Debug Module Tracing Debug Module Tracing can be enabled by navigating to IBSS gt Nodes gt Node Name where Node Name is the node that executed the request Enabling tracing provides additional information about the Module where tracing was enabled in the logs The addition logs are also logged along with the usual application logs Logs can be found in the Error Logs section under Logs In the Node Name screen there is a dropdown for Debug Module Tracing The Modules that can be traced using this option are All Assembly Manager SoftRater Batch ExecQueue JMS SoftRater Batch SoftRater Web Services Task Manager WorkManager Remote Call Softrater Cache Softrater Locator Connector Service 67 Chapter 11 IBSS Functionality in Java IBSS Ul Each module logs particular details and the Debug tracing can be enabled only to those
18. i 1204 n CovCd v gt m i 1205 nz CovLimit v gt m i 1207 nz CovEff Date v gt lc c i 9 desc Endorsement gt m i 1181 n EndorCd v gt m i 1182 n EndorRatelnd v gt m i 1190 n EndorEff_ Date v gt m i 1191 n Parm5 v gt lt c gt lt c gt lt c gt lt rate gt Insbridge XML Result Format lt result lob 2 st 6 gen_date 2 19 2014 1 55 32 PM gt 56 lt program parent_id 900 program_id 1 program_ver 1 status PASS gt c i 5 gt m i Dwelling_1 v 640 gt m i Dwelling_3 v 0 gt m i Dwelling_5 v 0 gt m i replec v 0 gt lt m i COV Replacement Cost Contents v 0 gt lt m i COV Mortgage Payment v 0 gt lt m i Dwelling_10 v 0 gt m i Dwelling_11 v 34 gt m i COV Replacement Cost Dwelling v 0 gt m i Dwelling 13 v 0 gt m iz Dwelling 13 v 674 gt m i COV Business Pursuits v 0 gt m i COV Permitted Incidental Occupancies v 0 gt m i COV Personal Injury v 0 gt m i Dwelling_17 v 0 02 gt lt m i Dwelling_18 v 0 gt lt m i Dwelling_19 v 0 gt lt m i CREDIT Multi Policy Discount v 0 gt lt m i CREDIT Neighborhood Watch v 0 gt lt m i CREDIT New Home v 0 20 gt Chapter 10 Insbridge XML Java Example lt m i CREDIT New Loan v 0 10 gt lt m i CREDIT Protective Devices v 0 020000000 gt lt m i Dwel
19. if possible and appropriate results are generated in the output XML Example lt heading gt lt program parent_id 700 program_id 24 program_ver 1 gt 20 Chapter 6 Insbridge XML Windows Example lt program parent_id 700 program_id 22 program_ver 1 gt lt heading gt lt program gt Node The lt program gt node specifies a specific SoftRater Package rating engine logic instance to run this rate request against A program typically represents rating logic for a particular State and line of business e g Texas Auto insurance California Home insurance The program node attributes are defined as follows parent_id Insbridge identifier typically assigned to a carrier for database lookup purposes Required program_id Insbridge identifier assigned to a program rating engine logic instance which represent the rating rules necessary to generate a quote Optional program_ver A particular version of a program Each version may have different rating rules inputs outputs etc Optional Attribute Requirement Rules 1 If the program id is provided then the version program ver value is used to select a program version to be processed against the source XML Example program parent_id 1 program idz 100 ver 3 gt 2 fthe program id is provided and the program ver is not the version selection rules for the program identified by program id are used to select the program version to be processed
20. users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc AMD Opteron the AMD logo and the AMD Opteron logo are trademarks
21. 4 R48 July 2014 Update Release vi Chapter 1 INTRODUCTION TO SOFTRATER SoftRater is the rating engine portion of the Oracle Insurance Insbridge Enterprise Rating IBER system The SoftRater rating engine is updated with logic created in RateManager and is the run time environment for a company s rates SoftRater supports request integration through a Web Services SOAP interface or through native Java or NET interfaces The engine is multi platform and has the ability to process rates in both a transactional and batch mode Issuance or Legacy System P gt Customer Extract Target Presentation Import User Services Request Web or ZP Presentation Application Customer Existing Policy Administration N SoftRater Service Boundary Optional SoftRater Transformation Support Engine Product Pricing Rating XML Database Target SoftRater engine accepts XML document requests User for rating processing or to extract product data for Existing Policy Portal or Agency Web presentation or workflow purposes System The following application sources are The SoftRater Engine performs all calculations supported by Oracle Insurance Insbridge and runs underwriting rules The output is Enterprise Rating Insbridge XML that is reformatted for distribution to all application sources e Web applications e Server based applications e Mainframe applications e Or any combination of the above For
22. 5 AM Next Runtime 2014 05 29 11 46 15 AM NAME Process Pending Requests Interval Every 10 0 second s Running Count 0 Last Runtime 2014 05 29 11 41 15 AM Next Runtime 2014 05 29 11 41 25 AM NAME Cache Threshold Max Watcher Interval Every 15 minute s Running Count 0 Last Runtime 2014 05 29 11 41 15 AM Next Runtime 2014 05 29 11 56 15 AM NAME Project Temp File Cleanup Interval Every 24 hour s Running Count 0 Last Runtime 2014 05 29 11 41 15 AM Next Runtime 2014 05 30 11 41 15 AM Figure 4 IBSS Task Manager The View Tasks option lists all the tasks running for a particular node with the details of the Task Name Interval between each execution Last Runtime and Next Runtime This feature also details when the next task execution should take place 64 Chapter 11 IBSS Functionality in Java SECURITY AUTHENTICATION Security Authentication is the layer between the IBSS application and the end user This layer is intended to provide the first level of security to the IBSS application by providing User Authentication based on user preference If the Security option is enabled the IBSS application prompts users for a password in order to gain access to IBSS If the Security option is disabled the application opens up normally to anyone with the correct URL Security can be enabled disabled on the Security page Features that are a part of the Security Authentication e Security Option Enabled Disabled e Change Pas
23. 6 17 41 43 Result Group Enabled 22 48 Result Node Example 25 51 Output XML 20 46 result def 21 47 result def name 21 48 Root Level Error Node Created 18 43 Rules Attribute 21 47 S SaveMapping Web Services Interface 13 Security 65 Security Authentication 65 Server Restarted or Shutdown SoftRater 11 Setting Options Result Documents 16 17 41 43 Several Rates Requesting 33 57 Single Quote Invalid Characters 46 Single Rate Request Example 33 56 site instance Attributes 51 SOAP Options 17 43 Supported Operations 12 SOAP Versions 70 SoftRater Definition v Engine Perform 7 Input Overrides 27 53 SoftRater Engine Processing 12 75 Index Rating Arguments 16 41 SoftRater Explorer Configuration Settings Updated 11 SoftRater Server Overview 60 SoftRater Web Service 13 SoftRater WSI Processing XML Data 17 43 SoftRaterEJB Engine Start Processing 32 55 Stop Processing 32 55 SoftRaterEJB jar Target JAR 36 Software Integration 12 36 Status Attributes 25 31 51 54 Statuses Aborted 63 Cancelled 63 Completed 63 Failed 63 Message Process 63 Pending 63 Processing 63 Submit Insbridge XML IBSS 42 Submitting Rate Requests via XML 19 45 Subscriber Identifier 17 43 Support 71 Supported Operations 12 T Target Environment Options 41 Target JAR 36 Task Manager 64 Time Statistics 32 55 Example 32 55 Trac
24. DI Path IBSS ins ru sr bsn 1 0 0 SoftRaterEJB com oracle ins ru sr bsn ejb engine SoftRater e SoftData EJB JNDI Path IBSS ins ru sr bsn 1 0 0 SoftDataEJB com oracle ins ru sr bsn ejb softdata SoftData e SoftServices EJB JNDI Path IBSS ins ru sr bsn 1 0 0 SoftServicesEJB com oracle ins ru sr bsn ejb softservices SoftServices e Timer EJB JNDI Path IBSS ins ru sr bsn 1 0 0 IBSSTimerService com oracle ins ru sr bsn ejb timer IBSSTimerService Interface Example package com oracle ins ru sr bsn ejb engine import javax ejb EJBException import javax ejb Remote jos Remote interface for Enterprise Bean SoftRater Ki Remote public interface SoftRater public String getDefaultPath throws EJBException public String getVersion throws EJBException public String ProcessIB final String aXMLInput final boolean aAddRoot final boolean aAddInputs final boolean aAddHeading final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean alnStyle final boolean aDoDebugOutput throws EJBException public String ProcessRequest final String aXMLInput final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading 37 Chapter 7 SoftRater Integration for Java 38 final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean aAddWorksheet final int aDoDebugOutput final boolean aDisableCache final String aTargetEnvironment final int aUseResultEn
25. Java SoftRater utilizes Microsoft SQL Server 2005 SP 4 and 2008 R2 Oracle 10g and 11g and IBM DB2 v9 5 for data store For Windows SoftRater utilizes Microsoft SQL Server 2005 SP 4 and 2008 R2 for data store The platforms for SoftRater engines are e SoftRater for Windows e SoftRater for Java consisting of SoftRater for WebSphere SoftRater for WebLogic SoftRater for JBoss Chapter 1 Introduction to SoftRater SoftRater for Windows e SoftRater for Windows supports Microsoft SQL Server 2005 SP 4 and 2008 R2 SoftRater for Java e SoftRater for JBoss supports Red Hat JBoss Application Server Versions 6 0 1 GA and 7 1 1 Version 6 0 1 GA Enterprise version Version 7 1 1 Version Name Final Built on 2012 03 09 e SoftRater for WebSphere supports IBM WebSphere V 7 0 and V 6 1 Version 7 0 0 7 Version Name Integrated Solutions Console Build cf70942 55 Built on 10 24 09 Version 6 1 0 0 Version Name Integrated Solutions Console Build b0620 14 Built on 05 16 06 e SoftRater for WebLogic supports Oracle WebLogic Release 11gR1 10 3 2 Release 10 3 2 Version Name 11gR1 NOTE WebLogic Express WLX edition is not currently supported NOTE JBoss WebLogic and WebSphere operate in a variety of environments As long as the application server is compatible with the operating system then SoftRater for Java also will be compatible SoftRater for Java is installed and fu
26. L data out of the system Rating arguments are optional For optimal performance use arguments for your rating integration Values 0 False 1 True e Add Root Node Use default 0 If submitting multiple rate request documents this option is typically set to true to make the result document a valid XML document e Add Inputs Use default 0 When set to true the full request Insbridge XML document is returned in the result Insbridge XML document making the XML document much larger than normal e Add Heading Use default 0 When set to true the program name description information is returned in the result XML also e Add Result Descriptions Use default 0 When set to true each result item includes the RateManager variable result name along with the result id and value Making the result XML much larger Typically most integration operates on the result IDs and descriptions are not needed when building an automated system e Add Empty Results Use default 0 When set to true a defined result item whose value is empty i e blank is still created and returned blank in the resulting Insbridge XML If your program design requires a number of optional results you could have blank results items in your XML e Debug Output Use default 0 When set to false no debug report will be issued Set to true if you would like a debug report e EnvRef Use default blank When left blank the default environ
27. ORACLE INSURANCE Oracle Insurance Insbridge Enterprise Rating SoftRater User Guide Release 4 8 August 2014 ORACLE Copyright 2005 2014 Oracle and or its affiliates All rights reserved Oracle Insurance Insbridge Enterprise Rating SoftRater User Guide Release 4 8 x Part E54875 01 Library E54888 01 August 2014 Primary Author Mary Elizabeth Wiger This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing If this is software or related documentation that is delivered to the U S Government or anyone licensing it on behalf of the U S Government the following notice is applicable U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end
28. Proxy nana 14 2C 14 Javascript Web Services iore ee e ea t Eee e te ta Pa Er ee a aa 14 C Example Web Services Process Message 14 C Example Web Services Custom Message 15 RATING ARGUMENTS FOR WINDOWS nenea ana 16 CUSTOM XML ARGUMENTS FOR WINDOWS nenea 17 INSBRIDGE XML WINDOWS ESAMPLE nnn 19 Insbridge XML Request Fomat nennen 19 Insbridge XML Result Fomat nnne 24 Input Overrides Shopping Feature sse 27 ONE 32 CHAPTER 8 CHAPTER 9 CHAPTER 10 CHAPTER 11 NOTICE SUPPORT INDEX Contents SOFTWARE INTEGRATION FOR JAVA nenea nana 36 Software Integration Methode 36 RATING ARGUMENTS FOR JAVA enne nnne nana 41 CUSTOM XML ARGUMENTS FOR JAVA nenne 43 INSBRIDGE XML JAVA ENXAMPDLE eene 45 Insbridge XML Request Fomat nennen 45 Insbridge XML Result Fomat nnne nana 49 Examples eene cece 55 IBSS FUNCTIONALITIES IN JAVA 0 nnn 60 Setvices EE 60 Node Level Services nana nana 60 Application Level Services A 60 Insbridge Connector Service nn nana 61 Message re 63 Insbridge Task Manager 64 Security Authentication nue raya ata a E aaa al aa a ae cal a a 65 Security Option Enableciueabled nana 65 Change Ee te D 66 Tracing Logs e e EE e Pe i a E P a Et Pe aaa 67 Information Logs E 67 Rtl Ee out
29. SoftRater SoftRater Rate Operators pcmSoftRater MappedRateOperators rateOper new pemSoftRater MappedRateOperators ct ct Only for Input and or Output Transformations pemSoftRater MappedRateRequest rateRequest new SRTester pomSoftRater MappedRateRequest rateOper AddHeading 1 rateOper AddRoot 1 rateOper AddInputs 1 rateOper AddResultDesc 0 rateOper AddResultEmpty 0 rateOper DebugRate 0 rateOper EnvRef SR rateRequest Subscriber 1002 rateRequest Lob 1 rateRequest Program 106 rateRequest Version 3 rateRequest OutputMappingStateful false Setting the input output Transformation templates rateRequest InputMappingIdentifier customInputXslt xslt rateRequest OutputMappingIdentifier customOutputXslt xslt rateRequest InputMappingType pcmSoftRater MappingType CUSTOM rateRequest OutputMappingType pcmSoftRater MappingType CUSTOM string results ibSoftRater ProcessCustomMessage rateXml rateOper rateRequest Created using Visual Studio NET 2008 15 Chapter 4 RATING ARGUMENTS FOR WINDOWS Valid values for rating arguments are entered in these two operations ProcessCustomMessage lt ibRateOper gt rating arguments lt ibRateOper gt ProcessMessage lt MappedRateOperators gt rating arguments MappedRateOperators The SoftRater engine rating arguments control the handling of XM
30. Target Environment Add Result Descriptions Use default False When set to true each result item includes the RateManager variable result name along with the result id and value Making the result XML much larger Typically most integration operates on the result IDs and descriptions are not needed when building an automated system Add Results to DB Use default False When set to true the result information is added to the database table in the database environment provided by the Target Environment Add Root Node Use default False If submitting multiple rate request documents this option is typically set to true to make the result document a valid XML document Add Work Sheet Use default False When set to true the style sheet details are added to the response XML Debug Output Use default 0 When set to 0 no debug report will be issued Set to 1 if you would like a debug report Delete Input XML from Disk Use default False When set to true the Input XML file used for rating will be deleted from the disk after the response is received Disable Cache Use default False When set to false the application cache is enabled and the engine caches the program information for a faster and efficient rating Include Results In Response Use default False By default the results are stored in the DB and the response is returned to the user Setting the Include Results In Response to
31. YZ xmins gt lt program parent_id 1002 program_id 1 program_ver 1 package_date 2014 05 21T10 32 59 status PASS gen_type 0 region_format en US custom_id 3PAY gt c i 0 gt lt m i TOTAL_PREMIUM v 500 gt lc lt program gt program parent_id 1002 program_id 1 program_ver 1 package_date 2014 05 21T10 32 59 status PASS gen_type 0 region formatz en US custom_id 6PAY gt lt c i 0 gt m i TOTAL PREMIUM v 525 gt lc lt program gt lt program parent_id 1002 program_id 1 program_ver 1 package_date 2014 05 21T10 32 59 status PASS gen_type 0 region_format en US custom_id 9PAY gt lt c i 0 gt lt m i TOTAL_PREMIUM v 550 gt lt c gt lt program gt program parent_id 1002 program_id 1 program_ver 1 package_date 2014 05 21T10 32 59 status PASS gen_type 0 region_format en US custom_id BASE gt lt c i 0 gt m i TOTAL PREMIUM v2 475 lc lt program gt lt result gt 30 Chapter 6 Insbridge XML Windows Example lt worksheet gt Node The result lt worksheet gt node provides an XML envelope containing all of the formatted data setup in the RateManager application as worksheet output for the program There can be 1 lt worksheet gt node group per program in the input lt rate gt XML document If the original lt rate gt request contained multiple lt program gt nodes in the heading node each program version locate
32. against the source XML Example program parent idz 1 program id 100 gt The program node allows mapped input overrides to be specified for a specific program in a multi program or multi state rate request See Multiple Rate Requests in a Single XML Document for more information result def Allows the user to override the default result mapping group by entering the output code By default SoftRater uses the group that is set up as the default in RateManager A different output group can be used by adding the attribute result def Output Code to the rate node where Output Code is the output code shown in RateManager Example program parent id 123 program idz 1 program verz 1 result defz FC42721399 result def name Allows the user to override the default result mapping group by entering the output group name By default SoftRater uses the group that is set up as the default in RateManager A different output group can be used by adding the attribute result def name Outout Group Name to the rate node where Output Group Name is the Output Group Name shown in RateManager Example program parent id 123 program id 1 program verz 1 result def namez RG Call AU BP 2 gt 21 Chapter 6 Insbridge XML Windows Example Home Program Explorer Controller PL 12 14 Output Mapping x Output Mapping Auto gt Controller PL 12 14 gt Version 1 i New W Create Package Z Test Program
33. am parent_id 1 program_id 318 program_ver 1 gt lt heading gt lt c i 0 desc Policy gt m i 1086 n PackageDisclnd v gt m i 1094 nz RenewalRetentionCreditlnd v gt m i 1157 n CompanyCode v gt m i 1212 nz Eff Date v gt m i 1214 nz PrimInsuredAge v gt m i 1215 nz SeclnsuredAge v gt m i 1222 n Renewallnd v gt lt c i 5 desc Home gt m i 1083 n TerritoryCode v gt m i 1084 nz ResidenceType v gt lt m i 1087 n ProtectionClass v gt m i 1095 nz Wood Tile SlateRoofType v gt m i 1096 nz HomeDeductible v gt m i 1098 nz WindstormOrHailDeductible v gt m i 1100 n CentralStationFireAlarmind v gt m i 1101 nz CentralStationBurglarAlarmInd v gt c i 8 desc Coverage gt m i 1204 n CovCd v gt m i 1205 n CovLimit v gt m i 1207 n CovEff_Date v gt lt c gt c i 9 desc Endorsement gt m i 1181 nz EndorCd v gt m i 1182 nz EndorRatelnd v gt lt m i 1190 n EndorEff_ Date v gt m i 1191 n Parm5 v gt 45 Chapter 10 Insbridge XML Java Example lt c gt lt c gt lt c gt lt rate gt lt rate gt Node The lt rate gt node marks the beginning of a rate request for a specific line of business This node has the required attribute lob which identifies the line of business for the request I
34. and step number used in the algorithm stepName The type of step being executed available by default stepNumber The step number in the algorithm available by default 31 Chapter 6 Insbridge XML Windows Example Example step stepName arithmetic stepNumber 1 gt lt term gt Node A subset of the step node This node identifies the values being used at the time of execution The type of term being used termType Variable operator and so on available by default valeam The name or type of the variable Only if value returned Constants operator and so on being used do not have a value returned d Current value at this point in the Only if value returned operators execution do not have a value returned Example term termType inputVariable valueName Date1 2014 01 02 lt term gt Time Statistics Time tracking statistics can be included if enabled on the Insbridge Framework Administrator SoftRater Engine page A time node segment will be included in the Insbridge Response XML document returned from the engine Example lt stats gt lt start_time gt 02 06 2014 04 25 35 0280 PM lt start_time gt lt stop_time gt 02 06 2014 04 25 35 0316 PM lt stop_time gt lt running_time gt 36 lt running_time gt lt stats gt lt start_time gt The start time is the internal system tracking time from the just before the SoftRaterEJB engine starts any processing parsing or an
35. anings are slightly different The following sections describe how to interpret the output XML lt result gt Node The lt result gt node marks the beginning of a rate request result There is a one to one correspondence between lt rate gt nodes in the request XML to lt result gt nodes in the response XML The result node attributes are defined as follows lob line of business indicator corresponding to the lt rate gt request nodes lob attribute gen_date server creation timestamp indicating when this response was created As described previously tracking attributes on the lt rate gt node are returned in the result XML document as attributes in the lt result gt node Example rate lob 2 policyld A1206 gen date 2 9 2014 1 50 31 PM program Node The result program node provides an XML envelope containing all of the formatted data setup in the RateManager application as output results for the program There can be 1 N program node groups based on 1 N program node groups requested in the input rate XML document If the original rate request contained multiple program nodes in the heading node each program version located during execution will generate a program node in the result data The result XML program node attributes are defined as follows parent id Parent or Insbridge Company Identifier available by default program id Selected Program Identifier available by default v
36. as a hit A subsequent request with this same information would result in the information being found in the cache and a call to the database would not be necessary WHAT IS A CACHE Miss Anytime a value is not found in a mapped variable table for a specific set of criteria it is considered a cache miss All misses are stored in the cache however the Category Miss Buffer Purge can be set to purge a certain percentage of the misses Consider the following mapped variable table Variable Criteria Territory Code ZIP Code City County State 1 75080 Richardson Dallas Texas 2 75081 Richardson Dallas Texas 3 75082 Richardson Dallas Texas 4 75083 Richardson Dallas Texas 5 75085 Richardson Dallas Texas Then the following data request would be considered a miss and the default value for the mapped variable would be used ZIP Code 75084 City Richardson County Dallas State Texas If this same request had not been made previously then a call would be made to the database to retrieve the information When a value is not found in the database for the request the default value would be used and the information would be stored in the cache as a miss A subsequent request with this same information would result in the information being found in the cache and a call to the database would not be necessary unless the miss had been purged from the database Chapter 2 Introduction to SoftRater Caching
37. ate request against A program typically represents rating logic for a particular State and line of business e g Texas Auto insurance California Home insurance The program node attributes are defined as follows parent_id Insbridge identifier typically assigned to a carrier for database lookup purposes Required program_id Insbridge identifier assigned to a program rating engine logic instance which represent the rating rules necessary to generate a quote Optional program ver A particular version of a program Each version may have different rating rules inputs outputs etc Optional Attribute Requirement Rules 1 If the program id is provided then the version program ver value is used to select a program version to be processed against the source XML Example lt program parent_id 100 program_id 100 ver 3 gt 2 Ifthe program id is provided and the program ver is not the version selection rules for the program identified by program id are used to select the program version to be processed against the source XML Example program parent idz 100 program idz 100 gt The program node allows mapped input overrides to be specified for a specific program in a multi program or multi state rate request See Multiple Rate Requests in a Single XML Document for more information result def Allows the user to override the default result mapping group By default SoftRater uses the group that is set up as the
38. ater for WebLogic JBoss or WebSphere SERVICES LAYER This functionality enables a customer to keep track of the requests that are submitted to the engine for rating Services are provided in two layers e Node Level Services e Application Level Services Node Level Services A node is the endpoint of an IBSS instance Every instance of IBSS must have a node created Nodes have the advantage of allowing for clustered environments to be managed from one location Nodes are created and managed on the IBSS home page Node Level Services are used for controlling services for a particular node Node level services allow IBSS administrators to choose which node needs to be involved in or prevented from processing requests A selected node can be started individually to perform the engine operations alone or it can be stopped to exclude it from processing requests The node level services cannot configure the properties for services that run at the application level Application Level Services Application Level Services are services that run across the application or apply to a clustered environment Application level services allow IBSS administrators to start and stop services across all nodes configured in a clustered environment The administrator goes to one node to start or stop services The request is sent to every node configured in the cluster Success or failure messages are sent back for every member to the initiating IBSS instance
39. ation Typically the RateManager environment is only rated against during program development or to debug a rating issue This is usually done through Testing however it can be done through the SoftRater Test Interface as well Since the development environment is very dynamic caching would actually slow down rating in most cases Chapter 3 SOFTWARE INTEGRATION FOR WINDOWS The Web Service Interface WSI provides a platform environment and language neutral mechanism for business process interoperability using two common denominators of the Internet XML and HTTP The SoftRater WSI is supported through the use of Microsoft Internet Information Server IIS and ASP NET Supported operations are SOAP and HTTP POST In order to utilize the SoftRater rating arguments the document must be a SOAP envelope Upon request the URL configures an instance of the SoftRater Engine from those arguments and forwards the InsbridgeRate XML Input format to the SoftRater Engine for processing After the SoftRater Engine completes processing the result InsbridgeRate XML Output format is forwarded through HTTP back to the requesting process When rating custom XML the engine has the option of stateful rating The SoftRater WSI adds the contents of the rating results to the document that was submitted for rating This is an important consideration when constructing XSLT mapping files NOTE If you are submitting Insbridge XML using a testing
40. ava component will not be affected These updates are for any instance of SoftRater for Java engines only 70 Support CONTACTING SUPPORT If you need assistance with an Oracle Insurance Insbridge Enterprise Rating System product please log a Service Request using My Oracle Support at https support oracle com Oracle customers have access to electronic support through My Oracle Support For information visit http Awww oracle com pls topic lookup ctx acc amp id info or visit http www oracle com pls topic lookup ctx acc amp id trs if you are hearing impaired Address any additional inquiries to Oracle Corporation World Headquarters 500 Oracle Parkwa Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 oracle com 71 Index INDEX 1 N lt program gt node Groups 25 31 51 53 lt lt c gt Node 22 25 48 52 lt heading gt Node 20 47 lt input gt Node 26 52 lt m gt Node 22 26 49 52 lt program gt Node 21 25 31 47 51 53 Specifying Input Values 27 53 lt rate gt Node 20 46 lt result gt Node 25 50 lt running_time gt Node 32 55 lt start_time gt Node 32 55 lt stop_time gt Node 32 55 A Add Empty Results Options 16 41 Add Heading Options 16 41 Add Inputs Options 16 41 Add Inputs to DB Options 41 Add Result Descriptions Options 16 41 Add Results to DB Options 41 Add Root No
41. ce final String aTargetENV final String aXMLInput final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean aDoDebugOutput final boolean aDisableCache throws EJBException public String ValidateCacheUsingThreshold throws EJBException public String GetNodelnstanceName throws EJBException 40 Chapter 8 RATING ARGUMENTS FOR JAVA The SoftRater engine rating arguments control the handling of XML data out of the system Rating arguments are optional For optimal performance use the following arguments for your rating integration Add Empty Results Use default False When set to true a defined result item whose value is empty i e blank is still created and returned blank in the resulting Insbridge XML If your program design requires a number of optional results you could have blank results items in your XML Add Heading Use default False When set to true the program name description information is returned in the result XML also Add Inputs Use default False When set to true the full request Insbridge XML document is returned in the result Insbridge XML document making the XML document much larger than normal Add Inputs to DB Use default False When set to true the details of the input request are added to the database table in the database environment provided by the
42. che limit the older caches are purged by this process Process Pending Task The engine picks up only one request at a time and processes it When there are multiple requests submitted for batch processing the process pending task submits the pending tasks to the engine for rating while a request is being processed Task Cleanup Task The details of all the requests that are processed by the engine are added to the database The task cleanup task prevents the database from accumulating too much unwanted data Task cleanup listener deletes all the records of a processed request that are in the database for more than the specified interval Process Async Request Task Process async request listener polls the queue at a specified interval picks up any requests from the request queue and submits it to the engine for processing Chapter 11 IBSS Functionality in Java e Add Results to DB Task While rating a request from SoftRater in IBSS the request for asynchronous process stores the request to disk and processes it whereas for the synchronous process the request and the response are rated just from memory and the response in returned to the user This task stores the details of these requests to the database for future reference MESSAGE PROCESS The service layer functionality allows you to keep track of the requests that are submitted to the engine for rating Various request types like Batch Rating Impact Analysis JMS Request and
43. coding final String aUseResultDefinition final boolean aAddlnputsToDb final boolean aAddResultsToDb throws EJBException public String ReceiveAsyncRequest final String albDocld throws EJBException public String ProcessRequestFromDisk final String aXMLInput final String aXMLResult final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean aAddWorksheet final int aDoDebugOutput final boolean aDisableCache final String aTargetEnvironment final int aUseResultEncoding final String aUseResultDefinition final boolean aDeletelnputXmIFromDisk final boolean aAddInputsToDb final boolean aAddResultsToDb throws EJBException public String ProcessRequestFromDb final String aXMLInputBatchld final String aXMLInputRefld final String aXMLResultBatchld final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean aAddWorksheet final int aDoDebugOutput final boolean aDisableCache final String aTargetSubscriber final String aTargetEnvironment final int aUseResultEncoding final String aUseResultDefinition final boolean alncludeResultsInResponse throws EJBException public String ProcessCustom final String aXMLInput final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading
44. d 2 Back to back with different program versions This allows you to compare various input values or identical input values against different program versions and see how the results are affected 3 Different program versions This allows you to compare various input values or identical input values against different programs and see how the results are affected 4 Using Input Override for all versions with the Program Version left blank using versioning criteria This allows you to compare various input values or identical input values against different program versions based on the versioning criteria and see how the results are affected 5 Using Input Override for 1 version and without Input Override for the other versions and no version criteria Input Override do not have to apply to every rate request You can run the rate request using Input Override on one version and not on the other versions This still allows you to compare various input values or identical input values against different program versions and see how the results are affected Sample Use Case Alamere Insurance offers customers Payment Plans of Prepaid fullpay 3 Pay 6 Pay and 9 Pay Alamere Insurance wants to quote a customer using multiple Payment Plans so they can show the customer the Policy Premium for each available plan They can either submit 4 separate Insbridge rate requests to the SoftRater engine Example 1A or they can submit one Insbridge rate req
45. d during execution will generate a lt worksheet gt node in the result data The result XML worksheet node attributes are defined as follows worksheet gen_type available by default package_date Package date available by default Parent or Insbridge Company parent_id Identifier available by default program_id Selected Program Identifier available by default Selected Program Version program_ver available by default Identifier region_format Locale used by program available by default result_def Output group used available by default result_def_name Output group name used status Pass Fail status available by default Example base worksheet gen_type 0 package_date 2014 08 11T04 42 13 parent id 8659 program id 21 program verz 1 region format en US result def2 C7A5730473 result def namez Group 1 status PASS algorithm Node A subset of the Worksheet node This node identifies the algorithm being run Name of the category where the category name algorithm was created available by default item Category ID available by default name Algorithm name available by default Type of algorithm rating type underwriting or driver available by default assignment Example algorithm categoryName Policy item 1 namez AG Algorithm 1 type Rating step Node A subset of the algorithm node This node identifies the step type
46. de Options 16 41 Add Work Sheets Options 41 Addinputs Option 26 52 AddRoot Attribute 33 57 Ampersand amp Invalid Characters 46 Application Level Services 60 Applications Supported by Insbridge 7 ASP NET SoftRater WSI 12 Attribute env_def 20 46 result_def 21 47 48 Rules 21 47 Attributes AddRoot 33 57 c Node 22 25 48 52 company_nm 25 31 32 51 54 55 72 d 26 52 db rt INPUT BATCH ID 51 db rt INPUT FILE ID 51 do rt RESULT BATCH ID 51 desc 22 48 engine type 51 env def 20 46 50 gen date 25 50 i 22 23 26 48 49 52 ibdoc version 50 Line of Business 20 46 lob 20 25 46 50 m Node 22 49 n 23 26 49 52 parent id 21 47 PolicyNumber 20 46 50 Program Node 21 25 31 47 51 53 program id 21 25 31 47 51 53 54 program ver 21 47 Rate Node 20 46 renc 46 Results Node 25 50 site instance 51 Status 25 31 51 54 Tracking 20 46 V 23 26 49 52 ver 25 31 51 54 version nm 25 51 Attribute value Pair 23 49 Audit Logs 69 C CH Example 14 15 Cache Breakdown of 9 Defining a Hit 9 Defining a Miss 10 Disabled 11 Exceptions 11 Cache Hit Example 10 Cache Miss Example 10 Category Node Example 22 26 48 52 Top Level 22 26 48 52 Category Node Nested Example 22 26 48 52 Changing Password 66 Children Category Node 23 26 49 52 Rate Node 22 26 48 52 ClearCacheltem Web Services
47. default in RateManager To use a different result group add the attribute result _def Result_ Code to the rate node where Result Code is the Output Code shown in RateManager 47 Chapter 10 Insbridge XML Java Example Example lt program parent_id 123 program_id 1 program_ver 1 result_def FC42721399 gt result_def_name Allows the user to override the default result mapping group by entering the output group name By default SoftRater uses the group that is set up as the default in RateManager A different output group can be used by adding the attribute result_def_name Outout_Group_Name to the rate node where Output_Group_Name is the Output Group Name shown in RateManager Example lt program parent_id 123 program_id 1 program_ver 1 result def namez RG Call AU BP 2 gt Home E Program Explorer DI Controller PL 12 14 Output Mapping x Output Mapping Auto gt Controller PL 12 14 Versioni n CA New E Create Package Z Test Program Notes J Refresh Output Code 48A1714561 FC42721399 fo Group Name Type Last Updated Enable Default D V Output Separate In order for you to be able to use a result group it must have been Enabled when the package was created see the RateManager topic Editing Result Group Options RG_Call_AU_BP Output Group Jun 18 2014 6 15PM V v RG_Call_AU_BP_2 Output Group Jun 24 2014 1 39PM v Figure 2 SoftRater Switches
48. el Categories 22 26 48 52 J Javascript Example 14 JMS Listener 61 L Less Than Invalid Characters 46 Line of Business Attribute 20 46 lob Attributes 20 25 46 50 env def 46 Lob Identifier 17 43 Lost Password 66 74 M Map Node Children 23 26 49 52 Mapped Variable Storing Information 9 Mapped Variables Cache 9 10 Mapping Group Overriding 21 47 48 Message Process Statuses 63 Message Processing 63 Microsoft Internet Information Server SoftRater WSI 12 Microsoft SQL Server SoftRater 7 Multiple rate Nodes 35 59 Example 33 57 Multiple Line of Business Request Example 35 59 Multiple Program Nodes Example 33 58 Multiple Rate Request Example 33 57 Multiple State Request Example 35 58 N n Attribute 23 26 49 52 Node Category 22 25 48 52 Heading 20 47 Input 26 52 Map 22 26 49 52 Program 21 25 31 47 51 53 Rate 20 46 Result 25 50 Running Time 32 55 Start Time 32 55 Stop Time 32 55 Node Level Services 60 O Options MapRequest SOAP 17 43 Rating Integration 16 41 Output Data Marking Beginning 25 52 Output Format InsbridgeRate XML 12 Output XML Document 19 45 OutputErrorXPathLoc Identifier 18 43 OutputMappingldentifier Identifier 17 43 OutputMappingStateful Identifier 17 43 OutputMappingType Index Identifier 17 43 OutputSchema Identifier 18 44 Overriding Default Character Encoding 46 Default Mapp
49. ent id 200 program id 32 ver 4 company nmz Alamere program nm Texas 6 Month ver nmz Performance status PASS 51 Chapter 10 Insbridge XML Java Example lt c gt Node Category The c category node marks the beginning of output data for a specific category of information e home car driver policy etc It has the following attributes i identifier Zero always indicates Policy level inputs other categories are user defined available by default d description of category with AddResultDesc request option Example c i 0 d Policy gt The Policy category is always a direct child of the lt program gt node It is also typically the top level category node The Policy category node typically has an ID of zero i e i 0 Item level user defined categories are nested under the Policy category node Example c i 0 gt m i SELECTED_TEIR v SPECIAL gt m i Total Policy Premium v 674 gt c i 5 gt lt m i Dwelling_1 v 640 gt m i Dwelling_3 v 0 gt m i Dwelling_5 v 0 gt m i SEC_II Personal Liability Each Occurrence v 500000 gt m i SEC_II Medical Payments Each Person v 2000 gt Ic lc m Node Map The m map node represents an individual attribute value pair mapped for a specific SoftRater Package hosted by SoftRater In the output case it identifies an output attribute as defined in the SoftRater Package repr
50. er Selected Program Version Identifier available by default Status Status of program rate request company nm Parent Corporate name with AddHeading request option program nm Program name with AddHeading request option version nm Example base Version name available by default with AddHeading request option program parent id 500 program id 3 ver 2 status PASS gt Example with AddHeading option requested program parent id 200 program id 32 verz 4 company nmz Alamere program nmz Texas 6 Month ver nmz Performance status PASS c Node Category The c category node marks the beginning of output data for a specific category of information i e home car driver policy etc It has the following attributes 25 Chapter 6 Insbridge XML Windows Example i identifier Zero always indicates Policy level inputs other categories are user defined available by default d description of category with AddResultDesc request option Example c i 0 d Policy gt The Policy category is always a direct child of the lt program gt node It is also typically the top level category node The Policy category node typically has an ID of zero i e i 0 Item level user defined categories are nested under the Policy category node Example c i 0 gt m i SELECTED_TEIR v SPECIAL gt lt m i Total Policy Premi
51. ered in the New Password and Confirm Password fields do not match then error message Passwords do not match is displayed in the screen e When the mandatory fields are updated the password value is encrypted e This encrypted new password value is updated in the insbridge configuration xml file Resetting the Password For security purposes information regarding resetting a lost or forgotten password is not included in this help document For information regarding these please log a Service Request using My Oracle Support at https support oracle com 66 Chapter 11 IBSS Functionality in Java TRACING LOGS When a request is submitted for execution to the engine the user does not have any idea of what is happening to the request or what the status is until the end response is received If the request fails for some reason the user would be unaware of what went wrong without logs Logs provide the ability to check the status of the request execution by providing step by step information on the execution process Logs play a vital role in the application to track the request execution and also to provide the error details Logs can be categorized in to the following types e Information Logs e Error Logs e Audit Logs Information Logs Information logs contain information regarding the request execution Unlike Error Logs information logs inform the user about other processes such as what process is currently being executed
52. esented by the program node and its associated value The m node s attributes are defined as follows i output identifier available by default n name description of output with AddResultDesc request option V value of output available by default The m node is always a child of a c category node and is an attribute value pair for that specific category instance see the category example above rate Node Input Document The rate node is optional When the rate request is issued with the Addinputs option this node is returned in the result XML document It includes the full input rate request document that was used to generate the rate result document 52 Chapter 10 Insbridge XML Java Example Example lt result lob 1 policyld ABC1234 AUTO gen_date 2 9 2014 1 50 31 PM gt rate policyld ABC1234 AUTO gt lt rate gt lt result gt Input Overrides By specifying input values in the lt program gt node within the lt header gt section of the input XML those values will be used for that program when it is processed by SoftRater regardless of whether those values are present in the body of the XML request This allows each program found in the header to use the common set of inputs provided in the rate request body and either provide additional inputs that are relevant only to that program or provide overriding inputs values to ones found in the body for use during rat
53. ess Pursuits v 0 gt lt m i COV Permitted Incidental Occupancies v 0 gt m i COV Personal Injury v 0 gt m i Dwelling_17 v 0 02 gt lt m i Dwelling_18 v 0 gt m i Dwelling_19 v 0 gt lt m i CREDIT Multi Policy Discount v 0 gt lt m i CREDIT Neighborhood Watch v 0 gt lt m i CREDIT New Home v 0 20 gt lt m i CREDIT New Loan v 0 10 gt lt m i CREDIT Protective Devices v 0 020000000 gt lt m i Dwelling_25 v 0 gt m i SEC_ C Personal Property v 213500 gt m iz SEC D Loss of Use v 122000 gt m iz SEC A Dwelling v 305000 gt m iz SEC I Personal Liability Each Occurrence v 500000 gt m i SEC_II Medical Payments Each Person v 2000 gt m iz SEC B Other Structures v 30500 gt m i Total Annual Premium v 674 gt m i DED Standard Deductible v 1000 gt m i COV Replacement Cost Comp v 1 gt m i Total Earthquake Annual Prem v 0 gt m i EQ Loss of Use v 25000 gt m i EQ Personal Property v 152500 gt m i EQ Dwelling Limit v 305000 gt m i DED Earthquake Deductible v 30500 gt Ic c i 0 gt m iz SELECTED TEIR v SPECIAL gt m i Total Policy Premium v 674 gt c lt program gt lt result gt 24 Chapter 6 Insbridge XML Windows Example The same nodes are present in the output XML as were found in the input XML however their me
54. gt Config gt Security In the Security screen the required option can be selected and saved Once successfully logged in Logout appears on the top right corner of the left frame of home screen This indicates that a separate session is established for the user and the user has the ability to logout of the session whenever needed Clicking Logout logs you out of the session and the Authentication screen is displayed if the security is enabled 65 Chapter 11 IBSS Functionality in Java Change Password When Security is enabled a default user admin with a default password of insbridge is assigned This is the user name and password to be used the first time you enter IBSS Changing Default Password for Security Authentication 1 From the IBSS home page navigate to security 2 Under the security menu select the option to Change Password The Change Password screen is displayed 3 Enter the default password in the Old Password field 4 Enter a password of your choosing in the New Password field Passwords should be between 5 12 characters 5 Click Update to update your password Password Rules and Behavior e Ifthe length of the password entered in any field is less than 5 characters the error message Password length should be between 5 12 characters is displayed next to the corresponding text field e The Update button gets enabled only when all the three fields are populated e Ifthe values ent
55. ier of the Line Of Business Subscriber Identifier of the Subscriber Program Identifier of the Program Version Identifier of the Program Version InputMappingldentifier Name of the Custom Mapping Document InputMappingType Integer for the Custom Mapping Document 0 None no input mapping should be performed 1 Global input mapping is global to the Line of Business Mapping name required 2 Local input mapping is unique to the program version 3 Custom input mapping of the customer that has been added into the workflow Mapping name required OutputMappingldentifier Name of the Custom Mapping Document OutputMappingType Integer for the Custom Mapping Document 0 None no output mapping should be performed 1 Global output mapping is global to the Line of Business 2 Local output mapping is unique to the program version 3 Custom output mapping of the customer that has been added into the workflow OutputMappingStateful The SoftRater WSI will add the contents of the rating results to the document that was submitted for rating OutputErrorXPathLoc Location of any system errors that occurred during the web service request that are not related to SoftRater By default an error node is created at the root level UseResultEncoding Setting should be set to 1 This allows encoding 0 no encoding No encoding may result in errors if special characters are submitted in the XML UseResultDefinition The re
56. indows Only Insbridge supports Platform Level Authentication using IIS and Windows Both endpoints must be in the same domain Windows authentication can be used Message Level Authentication and Application Level Authentication are not supported Using External Testing Tools If you are submitting the SOAP request using an external third party testing tool such as eviware soapUI you may need to wrap your rating request in a CDATA wrapper Please refer to the WSDL for the SOAP parameter data types and valid values Using CDATA IBDOC and CDATA are containers for the input XML for NET SOAP For Java SOAP no IBDOC is used only CDATA is used as follows Chapter 3 Software Integration for Windows lt XMLInputs xsi type xsd string gt lt CDATA custom XML l gt lt XMLInputs gt NOTE f you are submitting Insbridge XML you should use HTTP POST instead of SOAP SOAP should be used only when submitting custom XML SOAP Example HTTP SOAP Proxy When using a testing tool choose http lt yourserver gt ibfa connectors softrater asmx and add WSDL to the end of the URL http lt yourserver gt ibfa connectors softrater asmx WSDL Examples JavaScript Web Services var MyResults var MyXMLDoc var AppURL var obj HTTP MyXMLDoc ibDoc lt ibdoc gt lt rate gt lt rate gt lt ibdoc gt Well formed InsbridgeRate XML Input or CustomXml AppURL http yourserver ibfa Connectors softra
57. ing For more on using Input Overrides please see Input Overrides Shopping Feature on page 27 Example lt rate lob 1 gt lt heading gt lt program parent_id 2 program_id 1 program_ver 3 gt lt c i 0 d Policy gt m i 11 n Policy Program Specific Something v 1029 gt m i 12 n Custom Question 1 v XYZ gt c i 3 d driver gt m i 2 n gender v Female gt m i 3 n Custom Driver Question 1 v ABC gt lt c gt lt c gt lt program gt lt program parent_id 2 program_id 7 program_ver 3 gt lt heading gt c i 0 d Policy gt m i 11 nz Policy Program Specific Something v 5000 gt c i 3 d driver gt m i 3 n Custom Driver Question 1 v DEF gt lt rate gt lt worksheet gt Node The result lt worksheet gt node provides an XML envelope containing all of the formatted data setup in the RateManager application as worksheet output for the program There can be 1 lt worksheet gt node group per program in the input lt rate gt XML document If the original lt rate gt request contained multiple lt program gt nodes in the heading node each program version located during execution will generate a lt worksheet gt node in the result data The result XML worksheet node attributes are defined as follows worksheet gen_type available by default 53 Chapter 10 Insbridge XML Java Example package_date Package date available by default
58. ing Group 21 47 48 Default Rating Environment 20 46 Overview ESI 69 SoftRater Server 60 P parent id Attributes 21 47 Password Changing 66 Resetting 66 Rules 66 Ping Web Services Interface 12 Policy Category Children 22 26 48 52 PolicyNumber Attributes 20 46 50 Process Message 14 ProcessAsyncMessage Web Services Interface 12 ProcessCustomMessage Web Services Interface 13 Processing Data In and Out of System 17 43 SoftRater Engine 12 ProcessMessage Web Services Interface 13 Program Identifier 17 43 Program Node Example 25 31 51 54 Program Node w Heading Option Request Example 25 51 Program Nodes In Header 20 47 program id Attributes 21 25 31 47 51 53 54 Example 21 47 Rules 21 47 program ver Attributes 21 47 Proxy Classes Generating 13 Purging Misses Cache 10 R Rate Node Example 20 46 Rate Request Node to Mark Beginning 20 46 Rate Request Document 19 45 Rate Request Result Marking Beginning 25 50 RateManager Environment Cache Exceptions 11 Rating Multiple Lines of Business 35 59 Multiple States 35 58 Rating Arguments 16 41 Rating Environment Overriding 20 46 Rating Integration Options 16 41 Rating Request Response XML 19 45 ReceiveAsyncMessage Web Services Interface 13 renc 46 Attributes 46 Request XML Result Nodes 25 50 Requirements Rate Node 20 46 Result Documents Setting Options 1
59. ing Logs 67 Tracking Attributes 20 46 U Update 76 Password 66 Use Result Encoding Options 41 UseResultDefinition Identifier 18 43 UseResultEncoding Identifier 43 V V Attribute 23 26 49 52 Variables Storing Mapped Variable Information 9 ver Attributes 25 31 51 54 Version Identifier 17 43 version nm Attributes 25 51 View Tasks 64 W Web Service Interface 12 Web Service Interface ASP Page 13 Web Services 14 WebSphere EJB component 36 WSDL Documents 13 WSI 12 X XML Insbridge 19 45 Invalid Characters 46 Usage in SoftRater 19 45 Usage in SoftRater WSI 12 XML Data Out of System 16 41 XML Document Example 19 45 Multiple Rate Requests 33 57 Returned 32 55 XML Envelope 25 31 51 53
60. ling_25 v 0 gt m iz SEC C Personal Property v 213500 gt m i SEC I D Loss of Use v 122000 gt m i SEC_ A Dwelling v 305000 gt m iz SEC ll Personal Liability Each Occurrence v 500000 gt m i SEC_II Medical Payments Each Person v 2000 gt m iz SEC B Other Structures v 30500 gt m i Total Annual Premium v 674 gt m i DED Standard Deductible v 1000 gt m i COV Replacement Cost Comp v 1 gt m i Total Earthquake Annual Prem v 0 gt m i EQ Loss of Use v 25000 gt m i EQ Personal Property v 152500 gt m i EQ Dwelling Limit v 305000 gt m i DED Earthquake Deductible v 30500 gt lt c gt c i 0 gt m i SELECTED_TEIR v SPECIAL gt lt m i Total Policy Premium v 674 gt lt c gt lt program gt lt result gt Multiple Rate Requests in a Single XML Document It is possible to request several rates from a single XML document These can be rates on different lines of business across different states and or different SoftRater Package versions You can do this by combining multiple lt rate gt request nodes in one single root node and submitting it for rating The root node can be anything however in the WSI call it is always lt ibdoc gt Multiple lt rate gt nodes This request XML lt ibdoc gt lt rate gt lt rate gt lt rate gt lt rate gt lt ibdoc gt will produce this resu
61. lt XML lt ibdoc gt lt result gt lt result gt lt result gt lt result gt lt ibdoc gt The root node is not returned in the result XML automatically It must be specified in the call using the AddRoot attribute 57 Chapter 10 Insbridge XML Java Example Multiple lt program gt nodes This request XML lt ibdoc gt lt rate gt lt heading gt lt program gt lt program gt lt program gt lt program gt lt heading gt lt C gt lt C gt lt rate gt lt ibdoc gt will produce this result XML lt ibdoc gt lt result gt lt program gt lt C gt lt C gt lt program gt lt program gt C c lt program gt lt result gt lt ibdoc gt Multi State Request To rate against multiple states using one request XML document it is recommended to follow the Multiple lt program gt nodes request model In the following example we are targeting two Auto programs for rating A program typically represents a State for a specific line of business In this example we will assume CA 21 and TX 41 As discussed earlier in Input Overrides each program entry can specify input values to be used for that particular program This rate request XML Results for CA lt ibdoc gt lt rate lob 1 gt lt heading gt lt program parent_id 2 program_id 21 gt lt program gt lt program parent_id 2 program_id 41 gt l
62. ment defined in setup will be used To specifically define an environment enter in the environment name Entering a value here overrides any value entered in the file If no arguments are sent the default values will be used Chapter 5 CUSTOM XML ARGUMENTS FOR WINDOWS The SoftRater WSI controls the processing transformations of XML data in and or out of the system Custom XML arguments are required only when you are submitting custom XML If you are using Insbridge XML custom XML arguments are not required The information will be contained in the Insbridge XML If you are using custom XML and do not define the custom XML arguments any error message will be thrown Valid values for custom XML arguments are entered in these two operations ProcessCustomMessage lt ibCustomOper gt rating arguments lt ibCustomOper gt ProcessMessage lt MappedRateRequest gt rating arguments lt MappedRateRequest gt Use the following options below for your custom rating integration e Lob Identifier of the Line of Business e Subscriber Identifier of the Subscriber e Program Identifier of the Program e Version Identifier of the Program Version e InputMappingldentifier Name of the Custom Mapping Document e InputMappingType Enum for the Custom Mapping Document NONE No input mapping should be performed GLOBAL Input mapping is global to the Line of Business Mapping name required LOCAL Input mapping is uni
63. mework Administrator see Introduction to Environments in the Insbridge Framework Administrator User Guide To rate against a different environment add the attribute env_def Env_Name to the rate node where Env Name is the name of the environment you wish to rate against PolicyNumber The unique identifier that is assigned to each and every rate request This helps in differentiating the various rate requests when doing a batch rate Required for batch rating Example lt rate lob 1 env_def Env_Name PolicyNumber XMLInput_ChangeAutoComplex_127 gt As an optional feature all other attributes provided on the lt rate gt node are collected as tracking attributes to be returned in the result XML document as attributes in the lt result gt node This allows the original rate request to be uniquely tracked with its result XML document by any identification elements available to the calling subsystem In the example below the policyld A1206 attribute value pair would be mirrored on the lt result gt node of the resulting output XML Example lt rate lob 2 policyld A1206 gt This rate request may be targeted to one or more rating logic instances based on what is found in the lt heading gt node lt heading gt Node The lt heading gt node serves only as a container for lt program gt nodes and has no attributes If multiple lt program gt nodes are found in the heading node then rating is performed for each node
64. modules The details about the modules being tracked by each tracing option are NOTE 68 All Assembly Process SoftRater Batch ExecQueue JMS SoftRater Batch SoftRater Web Services Task Manager WorkManager Remote Call SoftRater Cache SoftRater Locator Connector Service IBSS Ul This option enables tracing across all modules Selecting this option logs all details about the process This may make debugging a specific module difficult due to the level of information returned Make sure this is the option you want All the database related operations and the Assembly process operations like starting a batch request submitting a pending request and other request operations are logged under this module This can be used to trace errors with inputs to the engine All the operations related to the batch execution queue are logged in this module The Queue related operations like inserting a message into queue peek a message from queue are logged under the JMS Module All the Batch operations before submitting the request to the engine are logged under this module This module logs all the web service related operations All the Timer related operations like scheduling a task cancel a task and other details regarding the Task Listing are logged under this module Information regarding the job that is being executed the Connector Service information and how many threads are processing a request and
65. n the cache at the same time independent of one another i e removing or updating one does not remove or update any of the others Program Version Environment For more information see the following topics What is a Cache Hit What is a Cache Miss When is Information Removed from the Cache Cache Use Exceptions For information on configuring the cache see the Insbridge Framework Administrator topic Introduction to SoftRater Engine Configuration and the SoftRater Server topic Program Cache WHAT IS A CACHE HIT Any time a value is found in a mapped variable table for a specific set of criteria it is considered a cache hit All hits are stored in the cache For example consider the following mapped variable table Variable Criteria Territory Code ZIP Code City County State 1 75080 Richardson Dallas Texas 2 75081 Richardson Dallas Texas Chapter 2 Introduction to SoftRater Caching 3 75082 Richardson Dallas Texas 75083 Richardson Dallas Texas 75085 Richardson Dallas Texas Then the following data request would be considered a hit and a value of 3 would be stored for the mapped variable ZIP Code 75082 City Richardson County Dallas State Texas If this same request had not been made previously then a call would be made to the database to retrieve the information Once obtained the information would be stored in the cache
66. n the following example the lob attribute is set to 2 which represents Home insurance according to the Insbridge standard line of business see RateManager Admin User Guide The rate node attributes are defined as follows lob Line of business indicator per Insbridge standard lob codes Required env_def Allows the user to override the default rating environment By default SoftRater rates against the default environment as set up in the Insbridge Framework Administrator see Introduction to Environments in the Insbridge Framework Administrator User Guide To rate against a different environment add the attribute env_def Env_Name to the rate node where Env Name is the name of the environment you wish to rate against PolicyNumber The unique identifier that is assigned to each and every rate request This helps in differentiating the various rate requests when doing a batch rate Required for batch rating Example lt rate lob 1 env_def Env_Name PolicyNumber XMLInput_ChangeAutoComplex_127 gt renc Allows the user to instruct SoftRater to not encode XML characters that are not considered valid XML characters These characters are Ampersand amp Lessthan sign lt Greater than sign gt Double quotation marks Single quotation mark By default these characters are encoded in the result XML For example the ampersand is encoded as amp amp To override this default behavior add the a
67. nal String ax Mi Input final String aXMLInputTag final String aXMLResult final boolean aAddRoot final boolean aAddlnputs final boolean aAddHeading final boolean aAddResultDesc final boolean aAddResultThatAreEmpty final boolean aAddWorksheet final int aDoDebugOutput final boolean aDisableCache 39 Chapter 7 SoftRater Integration for Java final String aTargetEnvironment final int aLOB final int aCompanyld final int aProgramld final float aProgramVersion final int aUseResultEncoding final String aUseResultDefinition final short alnputMappingType final String alnputMappingldentifier final short aOutputMappingType final String aOutputMappingldentifier final boolean aOutputMappingStateFul final String aOutputErrorXpathLoc final boolean aDeletelnputXmlFrombDisk final boolean aAddInputsToDb final boolean aAddResultsToDb throws EJBException public void ClearCacheltem final String aTargetEnvironment final short aType final int aLOB final int aCompanyld final int aProgramld final float aProgramVersion throws EJBException public String QueryAvailableEnvironments throws EJBException public void SaveMapping final String aTargetEnvironment final String aFileName final String aStyleData final short aType throws EJBException public String getErrorMessage throws EJBException public void DbReleaseToPool throws EJBException public String ExecuteSoftRaterlnstan
68. nctions within application server The external resources that the application server resides in will not affect SoftRater for Java Guide Update Individual reference guides for SoftRater for WebSphere SoftRater for WebLogic and SoftRater for JBoss are consolidated under the SoftRater for Java title SoftRater for Java provides one central location to reference materials that apply to all Java platforms Chapters in this guide that pertain to SoftRater for Java are identified The SoftRater for Windows reference guide is also included in the SoftRater User Guide Chapters in this guide that pertain to SoftRater for Windows are indentified Chapter 2 INTRODUCTION TO SOFTRATER CACHING The SoftRater engine enables SoftRater to store information in memory This reduces the amount of information that must be pulled from the database and can improve rating time The SoftRater engine caches all data requests that are related to the program Requests that are not related to the program will not be cached For example table variable information will be cached in memory while global version lookups do not get cached P2P callouts are retrieved from the database the first time the call is made After that the information is stored in cache When cache is purged the callout information will be removed The cache is broken down by line of business program version and environment This means that information for the following could all exist i
69. ng time after all program execution and just before the SoftRaterEJB engine closes the Insbridge Response XML document which will be marshaled back to the integrating client lt running_time gt The running time is the different in Milliseconds from the start time and stop time It represents the transactional duration of the program processing the request NOTE Running Time is shown in milliseconds 107 seconds Examples Single Rate Request Insbridge XML Request Format rate lob 2 tracking attribute2 env_def gt heading program parent_id 700 program idz 24 program verz 1 lt heading gt lt c i 0 desc Policy gt 55 Chapter 10 Insbridge XML Java Example m i 1086 n PackageDisclnd v gt m i 1094 nz RenewalRetentionCreditlnd v gt m i 1157 n CompanyCode v gt m i 1212 nz Eff Date v gt m i 1214 nz PrimInsuredAge v gt m i 1215 nz SeclnsuredAge v gt m i 1222 n Renewallnd v gt lt c i 5 desc Home gt m i 1083 nz TerritoryCode v gt m i 1084 n ResidenceT ype v gt lt m i 1087 n ProtectionClass v gt m i 1095 nz Wood Tile SlateRoofType v gt m i 1096 n HomeDeductible v gt m i 1098 n WindstormOrHailDeductible v gt m i 1100 n CentralStationFireAlarmina v gt m i 1101 nz CentralStationBurglarAlarmInd v gt c i 8 desc Coverage gt lt m
70. node Example result lob 1 PolicyNumber XMLInput ChangeAutoComplex 127 env_def ORACLE_DR gen_date 201 4 05 20 01 02 45 PM ibdoc version 3 1 engine type weblogic site_location site_instance LOCAL db rt INPUT BATCH ID 2 db rt INPUT FILE ID 10 db rt RESULT BATCH ID 16 program Node The result program node provides an XML envelope containing all of the formatted data setup in the RateManager application as output results for the program There can be 1 N program node groups based on 1 N program node groups requested in the input rate XML document If the original rate request contained multiple program nodes in the heading node each program version located during execution will generate a program node in the result data The result XML program node attributes are defined as follows parent id Parent or Insbridge Company Identifier available by default program id Selected Program Identifier available by default ver Selected Program Version Identifier available by default Status Status of program rate request available by default company nm Parent Corporate name with AddHeading request option program nm Program name with AddHeading request option version nm Version name with AddHeading request option Example base program parent id 500 program id 3 ver 2 status PASS gt Example with add heading option requested program par
71. ntains 2 lt program gt nodes with one Program 1 using input overrides and one Program 2 using just the common inputs The SoftRater engine will process the lt program gt nodes sequentially So when the engine processes the first lt program gt node Program 1 it will use the common inputs and override input id 7 with a value of Spay When the engine processes the second lt program gt node Program 2 it will use all common inputs with no overrides as none were specified for the second program The engine will return each program s results in the order that they were in the rate request You can identify the program results by order or you can use a custom non Insbridge specific attribute in the lt program gt node that will be echoed out in the response In this example we used custom id NOTE The heading section can contain 1 n number of program nodes Sample Input Override Scenarios There are a few ways to use the Input Override feature depending on what you want to compare You can choose to use the same input values and compare different program versions or programs or you can use varying input values and compare different program versions or programs You can also select to use program versioning 27 Chapter 6 Insbridge XML Windows Example 1 Back to back using the same program version number This allows you to compare various input values against the same program and see how the results are affecte
72. o use IBSS gt Nodes gt lt Node_Name gt This WSDL URL is used by the client to access the exposed web service In order to access the web service methods the ServiceEndpointinterface SEI object of the corresponding web service is needed The SEI object is obtained by using the WSDL URL and the Service name of the web service The Service name details are provided in the each WSDL document This SEI object acts as the proxy and enables the user to access the web service methods EJB Direct JNDI interfacing The EJB interfaces for creating service clients that creates SoftRater instances e Target JAR InsBridgeEJB jar is part of the IBSS EAR WebLogic e SoftRater EJB JNDI Path SoftRaterEJBZcom oracle ins ru sr bsn ejb engine SoftRater e SoftData EJB JNDI Path SoftDataEJB com oracle ins ru sr osn ejb softdata SoftData e SoftServices EJB JNDI Path SoftServicesEJB com oracle ins ru sr osn ejb softservices SoftServices e Timer EJB JNDI Path IBSSTimerService com oracle ins ru sr osn ejb timer IBSSTimerService Chapter 7 SofiRater Integration for Java WebSphere e SoftRater EJB JNDI Path com oracle ins ru sr bsn ejb engine SoftRater e SoftData EJB JNDI Path com oracle ins ru sr bsn ejb softdata SoftData e SoftServices EJB JNDI Path com oracle ins ru sr bsn ejb softservices SoftServices e Timer EJB JNDI Path com oracle ins ru sr bsn ejb timer IBSSTimerService e SoftRater EJB JN
73. ode 20 46 renc Override Default 46 Result Node 25 51 result def Override Default 21 48 Single Rate Request 33 56 Time Statistics 32 55 XML Document 19 45 Exceptions Cache 11 G gen date Attributes 25 50 Greater Than Invalid Characters 46 H Heading Node Example 20 47 Program Nodes 20 47 HTTP Usage in SoftRater WSI 12 HTTP GET Supported Operations 12 HTTP POST 13 Supported Operations 12 HTTP SOAP Proxy 13 36 i Attribute 22 23 26 48 49 52 ibdoc_version Attributes 50 IBSS Overview 60 Submit Insbridge XML 42 IBSS Timer Service 61 62 identifier Attribute 22 48 Identifiers XML Arguments 17 43 IIS 73 Index SoftRater WSI 12 Include Results In Response Options 41 Information Logs 67 Input Data Marking Beginning 22 48 Input Format InsbridgeRate XML 12 Input Node Example 26 53 Input Overrides Example 53 Input Values Specifying 27 53 InputMappingldentifier Identifier 17 43 InputMappingType Identifier 17 43 Insbridge Connector Service 61 Insbridge Framework Administrator Configuring Cache 9 Disabling Cache 11 Setting Up Defaults 20 46 Insbridge Rate Request XML Document 19 45 Insbridge Rate Request Result XML Document Example 24 49 Insbridge Fwk APP EAR Target JAR 36 InsbridgeRate XML 12 Integration Software 12 Software 36 Interface Example 37 Interfaces EJB 36 Invalid Characters Overriding Default 46 Item lev
74. or registered trademarks of Advanced Micro Devices UNIX is a registered trademark of The Open Group This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services CONTENTS CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5 CHAPTER 6 CHAPTER 7 PREFACE seca saca aaa aaa ca a a a a A aa a aa e aa aaa ai HN V Uc ta til V Related Documents V GOnV6TnllOriS 2 222 222222222222 222222222222 22222222 222222222 aa Da 2 anra a nan aa aaa Pa cc aaa dul dada data do V System Heouirements nana ae vi Manual History vi INTRODUCTION TO SOFTRATER nenea nana nana 7 INTRODUCTION TO SOFTRATER CACHING nenea nea nana 9 What isa Cache Hit ss et bee eat 9 What is a Cache Mise 10 When is Information Removed from the Cache 11 Gache lse Exceplion s s sas eS RR ae aaa MERO 11 SOFTWARE INTEGRATION FOR WINDOWS sess 12 Web Services Interfaces for Windows a 12 Using e ME te 13 SOAP Example HTTP SOAP
75. que to the program version CUSTOM Input mapping of the customer that has been added into the workflow Mapping name required e OutputMappingldentifier Name of the Custom Mapping Document e OutputMappingType Enum for the Custom Mapping Document NONE No output mapping should be performed GLOBAL Output mapping is global to the Line of Business LOCAL Output mapping is unique to the program version CUSTOM Output mapping of the customer that has been added into the workflow e OutputMappingStateful The SoftRater WSI adds the contents of the rating results to the document that was submitted for rating Chapter 5 Custom XML Arguments for Windows NOTE NOTE OutputErrorXPathLoc Location of any system errors that occurred during the web service request that are not related to SoftRater for Windows By default an error node is created at the root level UseResultDefinition The result definition added to the response If you are using custom XML to rate or test the mapping name may need to be passed through The Input Mapping Type arguments Global and Custom require the name of the mapping file The OutputSchema web services argument is no longer being used This argument displayed the path of any schema that the WSI should validate against If you are currently using this you can leave it in the custom XML Chapter 6 INSBRIDGE XML WINDOWS EXAMPLE XML is the primary data exchange mechanism used b
76. resources and time to execute Consult with your system admin before configuring the number El Cg Nodes of jobs and listeners per JVM Node INSBRIDGE Connector Successfully started a SoftRater Node PRODUCTION A Connector Successfully Ca SoftData DBRuntime S Softtibraries amp M INSBRIDGE Batch Rating v Pending v View Messages Edit Process Configuration Cancel E PRODUCTION A If you see this message you have not requested a listing from the selected spoke client Clicking PRODUCTION B View Messages will provide you with a list view of the first in first out messages that are waiting to execute WE PRODUCTION C WE PRODUCTION D ss Help Insbridge Task Manager Properties The Insbridge Task Manager gives you the ability to execute tasks daily weekly hourly or by the minute INSBRIDGE Wiew Tasks This process may take a while to execute Task Process Time Figure 3 IBSS Services Page Insbridge Connector Service Properties The Insbridge Connector Service properties include e Batch processing properties such as the number of maximum simultaneous jobs and the maximum number of threads per Job that can be run by the engine to process a request 61 Chapter 11 IBSS Functionality in Java NOTE Email notifications on the success and or failure of batch processes Protocol host port user name and password properties should be configured prior to reque
77. s in a processing state it can be aborted 63 Chapter 11 IBSS Functionality in Java INSBRIDGE TASK MANAGER Insbridge Task Manager manages all the timer tasks associated with the IBSS Connector Service Task properties allow you to configure when tasks should be run These tasks are at the application level and apply to every node configured in the cluster The Insbridge Task Manager functionality includes e Setting the time interval for the execution of tasks This is done in the Properties window You can Enter the properties for Project Temp File Cleanup Delete Processed Requests Process Async JMS Requests Process Pending Requests Cache Threshold Max Watcher Add Result to DB e Settings can be set to be executed daily weekly hourly or by the minute Insbridge Task Manager Properties The Insbridge Task Manager gives you the ability to execute tasks daily weekly hourly or by the minute LOCAL v i This process may take a while to execute Task Process Time 2014 05 29 11 41 17 731 NAME Clean up Completed Tasks Interval Every 1440 minute s Running Count 0 Last Runtime 2014 05 29 11 41 15 AM Next Runtime 2014 05 30 11 41 15 AM NAME Process Async JMS Requests Interval Every 5 minute s Running Count 0 Last Runtime 2014 05 29 11 41 15 AM Next Runtime 2014 05 29 11 46 15 AM NAME Add Result To DB Interval Every 5 minute s Running Count 0 Last Runtime 2014 05 29 11 41 1
78. se Rating Extended Services Interface ESI is a library module designed to provide remote services to the Insbridge Enterprise Rating IBER business services without directly utilizing the system User Interfaces Ul ESI is allows a user to create objects and insert the same to a database or process an Insbridge XML to runtime database The ESI functionality is explained in the ESI for Java User Guide available in the Oracle Technical Network http www oracle com technetwork documentation insurance 097481 html 69 Notice SOAP VERSION UPDATES The SoftRater for Java engines are now on the same SOAP version e SoftRater for WebSphere has been updated to SOAP version 1 1 e SoftRater for WebLogic has been updated to SOAP version 1 1 e SoftRater for JBoss has been updated to SOAP version 1 1 These changes mean that the WSDLs for the SoftRater for Java engines have been modified Updated WSDL documents will need to be incorporated into any client calling application that communicates with SoftRater If upgrades are done to the SoftRater for Java engines without updating the calling applications the calling application will fail Please update a test environment prior to deploying to production Install the EAR file in a test environment to obtain the WSDL Update your calling application and then test When testing is complete you can upgrade your other environments NOTE Customers running a Windows only environment without a J
79. ser Guide e You can view these guides in line at this address http www oracle com technetwork documentation insurance 097481 htm CONVENTIONS The following text conventions are used in this document Convention Description bold Boldface type indicates graphical user interface elements associated with an action Italic type indicates book titles emphasis or placeholder variables for which you Italic supply particular values Preface Monospace type indicates commands within a paragraph URLs code in EE examples text that appears on the screen or text that you enter SYSTEM REQUIREMENTS For minimum operating system and hardware requirements please see the Hardware Software requirements guide Manual History New editions incorporate any updates issued since the previous edition Edition Publication Product Publication Date Comment Number Version 15 Edition P01 721 15 R 4 0 April 2010 Update Version and Combine 16 Edition PO1 721 16 R 4 0 1 August 2010 Update Release 17 Edition PO1 721 17 R 4 1 December 2010 Update Release 18 Edition P01 721 18 R 4 5 May 2011 Update Release 19 Edition P01 721 19 R 4 5 1 September 2011 Update Release 20 Edition PO1 721 20 R 4 6 May 2012 Update Release 21 Edition P01 721 21 R 4 6 1 November 2012 Update Release 22 Edition P01 721 22 R 4 7 September 2013 Update Release 23 Edition P01 721 23 R 4 7 1 November 2013 Update Release 24 Edition P01 721 2
80. st processing The service cannot send notification emails until that information is entered and verified Offline processing using JMS Before posting a request to the queue queue location reply to location connection factory context factory and provider URL properties must be entered JMS must be setup in the application server prior to entering queue details The same values are entered in IBSS in the Insbridge Connector Services Properties After filling in the Connector Properties details make sure to test the connector properties using the Test Connector Properties button provided in the Connector Properties page A popup displays a success or failure message Also an email will be sent to the configured user JMS Successfully Sent and Received JMS Message EMAIL SMTP Successfully Sent Email IBSS Timer Service Starting the Insbridge Connector Service starts the IBSS Timer Service IBSS timer service is a group of listeners performing specific tasks at specified intervals Request messages reach the engine only when the timer service is started Other listeners that get started when the IBSS Connector Service starts include 62 Temp Cleanup Task The temp cleanup task runs at a specified interval This task cleans up the temp files that are created by the IBSS process Cache Controller Task The cache controller task checks the cache size limit at a specified interval If the cache size is greater than the maximum ca
81. sult definition is added to the response If you are using custom XML to rate or test the mapping name may need to be passed through The Input Mapping Type arguments Global and Custom require the name of the mapping file 43 NOTE The OutputSchema web services argument is no longer being used This argument displayed the path of any schema that the WSI should validate against If you are currently using this you can leave it in the custom XML 44 Chapter 10 INSBRIDGE XML JAVA EXAMPLE XML is the primary data exchange mechanism used by Oracle Insurance Insbridge Enterprise Rating system to communicate information electronically with external and internal software systems Insbridge s rating request input XML is designed to be flexible and efficient It allows for single or multiple rate requests to be submitted via one input XML document The rate requests embedded in this single document can be targeted to multiple states and or multiple lines of business Multiple versions of a rating package also can be targeted in a single rate request document The rating request response XML is also streamlined to present all the results to the various request methods described above in a single output XML document INSBRIDGE XML REQUEST FORMAT The following is an example of an Insbridge rate request XML document rate lob 2 tracking_attribute env_def PolicyNumber XMLInput_ChangeAutoComplex_127 gt lt heading gt lt progr
82. sword e Reset Password Security Option Enabled Disabled The Security option is enabled by default when the application is loaded for the first time Users will see the Authentication Screen where they are prompted for Username Password For the first login the default credentials have to be entered to log in to the IBSS application On successful login the user is placed on the IBSS home screen The Security Authentication adds a node Security to the Insbridge configuration xml document as below security password 159754A9 WBP6X SC9 type Custom username 2S29 Z4 0 gt security Node Name password Encrypted value of the password type Type of Security Authentication username Encrypted value of username The authentication screen is presented when the application is loaded for the first time to avoid click jacking and thereafter whenever the user logs in with the security feature enabled The authentication screen has 2 frames with the left frame containing the credentials text box and the right frame displaying the IBSS home screen along with node status All the features in the right frame are disabled You must log in to enable all the features on the right frame A successful login places you on the IBSS Home page If the login is not successful an error message Username amp Password do not match Please try again is displayed The security option can be enabled disabled on the Security screen IBSS
83. t program gt lt heading gt lt C gt lt C gt ka lt rate gt Results for TX lt ibdoc gt Will produce this result XML lt ibdoc gt result lob 1 gen date 2 9 2014 1 50 31 PM gt lt program parent_id 2 program_id 21 gt lt C gt lt C gt 58 Chapter 10 Insbridge XML Java Example lt program gt lt program parent_id 2 program_id 41 gt lt C gt lt C gt lt program gt lt result gt lt ibdoc gt Multi Line of Business Request To rate against multiple lines of business using one request XML documert it is recommended to follow the Multiple lt rate gt nodes request model In the following example we are targeting two lines of business for rating Auto and Home The lob attribute in the lt rate gt node signifies which line of business will be rated against This rate request XML lt ibdoc gt lt rate lob 1 gt lt rate gt rate lob 2 gt lt rate gt lt ibdoc gt Results for Auto Will produce this result XML lt ibdoc gt P4 lt result gt result lob 1 gen_date 2 9 2014 1 50 31 PM E result lob 2 gen_date 2 9 2014 1 50 45 PM gt lt result gt lt ibdoc gt Results for Home 59 Chapter 11 IBSS FUNCTIONALITIES IN JAVA Oracle Insurance Insbridge Enterprise Rating SoftRater Server IBSS is an administrative tool used in conjunction with SoftR
84. t and is not loaded in a system XML document object ProcessCustomMessage should be used for non NET communication i e Java to Java or Java to NET NET to NET communication also can use ProcessCustomMessage e ProcessMessage Obtain Rates from the Insbridge XEngine Custom XML is supported The return file is loaded into a system XML document object ProcessMessage should be used for NET to NET communication only e ReceiveAsyncMessage Obtain Rate Results from the Insbridge XEngine Rate Broker e SaveMapping The remote Engine location notification endpoint for custom mappings Used when the engine location is a remote Windows engine Used internally during a SoftRater node to SoftRater node communication Users should not call externally Using HTTP There are two HTTP Web Services 1 HTTP SOAP Proxy SoftRater Web Service From the WSDLs proxy classes can be generated in a SOAP supported development environment that communicate with the installed SoftRater instance The SoftRater Web Service WSDL is located at the following URL http yourserver ibfa connectors softrater asmx WSDL 2 HTTP POST A lite weight Web Service Interface An ASPX page is provided as an interface for clients with only web form POST abilities without using a SOAP envelope message CustomXml cannot be submitted from this interface The URL to the POST interface is http yourserver ibfa connectors softrater asmx ProcessMessage WS Security W
85. t m i COV Personal Injury v 0 gt 49 Chapter 10 Insbridge XML Java Example lt c gt m i Dwelling_17 v 0 02 gt lt m i Dwelling_18 v 0 gt lt m i Dwelling_19 v 0 gt lt m i CREDIT Multi Policy Discount v 0 gt lt m i CREDIT Neighborhood Watch v 0 gt lt m i CREDIT New Home v 0 20 gt lt m i CREDIT New Loan v 0 10 gt m i CREDIT Protective Devices v 0 020000000 gt lt m i Dwelling_25 v 0 gt m iz SEC C Personal Property v 213500 gt m iz SEC I D Loss of Use v 122000 gt m iz SEC A Dwelling v 305000 gt m iz SEC Il Personal Liability Each Occurrence v 500000 gt m i SEC_II Medical Payments Each Person v 2000 gt m iz SEC I B Other Structures v 30500 gt m i Total Annual Premium v 674 gt m i DED Standard Deductible v 1000 gt m i COV Replacement Cost Comp v 1 gt m i Total Earthquake Annual Prem v 0 gt m i EQ Loss of Use v 25000 gt m i EQ Personal Property v 152500 gt lt m i EQ Dwelling Limit v 305000 gt lt m i DED Earthquake Deductible v 30500 gt lt c i 0 gt Ic lt program gt lt result gt m i SELECTED_TEIR v SPECIAL gt lt m i Total Policy Premium v 674 gt The same nodes are present in the output XML as were found in the input XML however their meanings are slightly different lt result gt Node The
86. t values in the lt program gt node within the lt header gt section of the input XML those values will be used for that program when it is processed by SoftRater regardless of whether those values are present in the body of the XML request This allows each program found in the lt header gt to use the common set of inputs provided in the rate request body and either provide additional inputs that are relevant only to that program or provide overriding inputs values to ones found in the body for use during rating This functionality is sometimes referred to as Shopping as it allows requester to get multiple results for a single rate request using a different value for one or more inputs such as PayPlan and or Deductible The following shows the basic structure of an Insbridge XML using input overrides lt rate lob 125 gt lt heading gt i Eprogram parent id 1002 program id 1 program vers 1 custom Id 3PAY gt Program 1 with input overrides lt c i 0 desc Policy gt em i 7 n PaymentPlanCd v 3pay gt program id 1 program ver 1 custom id BASE gt Program 2 no input overrides lt c i 0 desc Policy gt lt m i 7 n PaymentPlanCd v Prepaid gt lt c i 1 desc Location gt lt mi 3 n LocationStateCd v AL gt m i 4 n SignsLimit v 2500 gt m i 6 n FullCoverageYN v N gt Rate Request Body Common Inputs i lc lc lt rate gt This rate request co
87. ter asmx ProcessCustomMessage Web Services Request URL objHTTP new ActiveXObject Msxml2 XMLHTTP Microsoft HT TP Request Object objHTTP open post AppURL false objHTTP setRequestHeader SOAPAction http insbridge net wsi Connector SoftRater ProcessCustomMessage Set the SOAP action objHTTP setRequestHeader Content Type application x www form urlencoded objHTTP send MyXMLDoc MyResults objHTTP responseXML returns XML response MyResults objHTTP responseT ext returns text response Optional C Example Web Services Process Message string rateXml File ReadAllText C NNInsbridge xml Rate an Instance pmSoftRater SoftRater ibSoftRater new pmSoftRater SoftRater Rate Operators pmSoftRater MappedRateOperators rateOper new pmSoftRater MappedRateOperators rateOper AddHeading 1 14 Chapter 3 Software Integration for Windows rateOper AddRoot 1 rateOper AddInputs 1 rateOper AddResultDesc 0 rateOper AddResultEmpty 0 rateOper DebugRate 0 rateOper EnvRef rm default ibSoftRater MappedRateOperatorsValue rateOper Rate using the ProcessMessage Servic string results ibSoftRater ProcessMessage rateXml OuterXml Created using Visual Studio NET 2008 C Example Web Services Custom Message string rateXml File ReadAllText C NNCustom xml Rate an Instance pemSoftRater SoftRater ibSoftRater new pcm
88. tetra Tre tT ve red aia ove 69 A qit De pup ES 69 ESI Extended Service Interface 69 SOAP VERSION UPDATES AAA 70 CONTAGTING SUPPORD rrr rrr rtr RR ERE RR ss 71 INDEX omn ENEE a a d d a aa Pa 72 LIST OF FIGURES FIGURE 1 OUTPUT CODE aaa aa a a a a a e a aa a a i ta 22 FIGURE 2 SOETRATER SWITCHES L ac ata aa a E E 48 el lee e ed EE 61 FIGURE 4 IBSS TASCKMANAGER aa ata aaa aa a a i a ai i a a 64 Preface PREFACE Welcome to the Oracle Insurance Insbridge Enterprise Rating SoftRater User Guide This guide describes the concepts and usage of Oracle Insurance Insbridge Enterprise Rating SoftRater SoftRater This guide is describes the concepts and requirements of SoftRater It provides a reference for developers to properly interact with the Insbridge SoftRater Engine either through SOAP POST Web Services Interface WSI or Direct EJB Interfacing This guide contains reference information on these SoftRater engines e SoftRater for Windows e SoftRater for WebSphere e SoftRater for WebLogic e SoftRater for JBoss AUDIENCE This guide is intended for SoftRater system administrators who are tasked with administering SoftRater Readers of this guide should be familiar with XML HTTP RELATED DOCUMENTS For more information refer to the following Oracle resources e The Oracle Insurance Insbridge Enterprise Rating Framework Administrator User Guide e The Oracle Insurance Insbridge Enterprise Rating SoftRater Server U
89. the node that active are logged under this module The remote operations such as engine execution and the remote proxy client operations are logged under this module The operations related to the Program Listing and other cache operations are logged using this module The EJB home locator details are logged using this module Connector Service operations such as starting a service are logged under this module UI operations such as Email configuration details are logged under this module In IBSS Error and Information logs are both located on the Error Logs page Error Logs can be viewed under IBSS gt Nodes gt lt Node_Name gt gt Logs gt Error Chapter 11 IBSS Functionality in Java Error Logs Error logs get logged whenever the application encounters an exception The exception can be with the request execution the request itself or with the properties configuration Details regarding the exception can be found in the error logs In IBSS the Error logs can be found under IBSS gt Nodes gt Node_Name gt Logs gt Error Audit Logs Audit logs are used for tracking the SoftRater engine operations The Audit logs contain information about the Engine categorized into three different operations XML SQL and SoftRater Runtime Export In IBSS the Audit logs can be found under IBSS gt Nodes gt Node_Name gt Logs gt Audit ESI EXTENDED SERVICE INTERFACE Oracle Insurance Insbridge Enterpri
90. tiple states using one request XML document it is recommended to follow the Multiple lt program gt nodes request model In the following example we are targeting two Auto programs for rating A program typically represents a State for a specific line of business In this example we will assume CA 21 and TX 41 As discussed earlier in Input Overrides each program entry can specify input values to be used for that particular program This rate request XML lt ibdoc gt lt rate lob 1 gt lt heading gt program parent_id 2 program_id 21 gt lt program gt lt program parent_id 2 program_id 41 gt lt program gt lt heading gt lt C gt lt C gt lt rate gt lt ibdoc gt Will produce this result XML lt ibdoc gt result lob 1 gen date 2 9 2014 1 50 31 PM program parent id 2 program id 21 Results for CA lt C gt lt C gt lt program gt program parent_id 2 program_id 41 gt _ _ _ lt C gt lt C gt lt program gt lt result gt lt ibdoc gt Results for TX Multi Line of Business Request To rate against multiple lines of business using one request XML documert it is recommended to follow the Multiple lt rate gt nodes request model In the following example we are targeting two lines of business for rating Auto and Home The lob attribute in the
91. tool it is required to use HTTP POST instead of SOAP SOAP should only be used when rating custom XML If present or if you are using NET SOAP remove lt MappedRateRequest gt section from the SOAP header WEB SERVICES INTERFACES FOR WINDOWS SoftRater provides Web Service Interface for a SoftRater Rating XEngine The following operations are supported For a formal definition please review the Service Description found on your IBFA instance at http lt yourserver gt ibfa connectors softrater asmx e ClearCacheltem The remote Engine location notification for cache unloading Used when the engine location is a remote Windows engine Used internally during a SoftRater node to SoftRater node communication Users should not call externally e Ping This obtains the status of the Insbridge XEngine This method needs an XML document Id Subscriber ID The id attribute is required request id 200 gt Version is the version of the application For example remote version 04 08 00 x64 gt lt ping gt lt CDATA 3 5 0 gt lt ping gt lt remote gt Ping results are for the Engine used by Oracle Support e ProcessAsyncMessage Submit Rate Request to the Insbridge XEngine Rate Broker Insbridge XML only Chapter 3 Software Integration for Windows e ProcessCustomMessage Obtain Rates from the Insbridge XEngine using custom xml You also can use this method for an Insbridge XML request The Java returned is in string forma
92. true includes the result details with the response to the user Target Environment Required This field is mandatory and represents the database environment that is used for rating the request Use Result Encoding Use default False When set to true encoding will be done to special 41 characters Set to false if you would like to not use encoding Entering a value here will override any value entered in the file No encoding may result in errors if special characters are submitted in the XML If no arguments are sent the default values will be used Default values are defined in setup If using SoftRater Server see Submit Insbridge XML in the IBSS User Guide To navigate to the Submit Insbridge XML page select the Submit Insbridge XML link available from the menu tree on the SoftRater page of IBSS This page allows you to rate an input file that is in the Insbridge XML format 42 Chapter 9 CUSTOM XML ARGUMENTS FOR JAVA The SoftRater WSI controls the processing transformations of XML data in and or out of the system Custom XML arguments are required only when you are submitting custom XML If you are using Insbridge XML custom XML arguments are not required The information is contained in the Insbridge XML If you are using custom XML and do not define the custom XML arguments an error message will be thrown Use the following MapRequest SOAP options below for your rating integration NOTE Lob Identif
93. ttribute renc 1 to the rate node Example rate lob 1 renc 1 gt As an optional feature all other attributes provided on the lt rate gt node are collected as tracking attributes to be returned in the result XML document as attributes in the lt result gt node This allows the original rate request to be uniquely tracked with its result XML document by any identification elements available to the calling subsystem In the example below the PolicyldNumber XMLInput_ChangeAutoComplex_127 attribute value pair would be mirrored on the lt result gt node of the resulting output XML Example 46 Chapter 10 Insbridge XML Java Example rate lob 2 PolicyNumber XML Input _ChangeAutoComplex_127 gt This rate request may be targeted to one or more rating logic instances based on what is found in the lt heading gt node lt heading gt Node The lt heading gt node serves only as a container for lt program gt nodes and has no attributes If multiple lt program gt nodes are found in the heading node then rating is performed for each node if possible and appropriate results are generated in the output XML Example lt heading gt lt program parent_id 700 program_id 24 program_ver 1 gt lt program parent_id 700 program_id 22 program_ver 1 gt lt heading gt lt program gt Node The lt program gt node specifies a specific SoftRater Package rating engine logic instance to run this r
94. uest using the Input Overrides Shopping feature Example 1B Example 1A 4 separate Insbridge rate requests REQUEST 1 lt rate lob 125 gt lt heading gt lt program parent_id 1002 program_id 1 program_ver 1 gt lt heading gt lt c i 0 desc Policy gt m i 7 nz PaymentPlanCd v 3pay gt lt c i 1 desc Location gt m i 3 n LocationStateCd v AL gt m i 4 n SignsLimit v 2500 gt m i 6 n FullCoverageYN v N gt lc lc lt rate gt REQUEST 2 lt rate lob 125 gt lt heading gt lt program parent_id 1002 program_id 1 program_ver 1 gt lt heading gt lt c i 0 desc Policy gt m iz 7 nz PaymentPlanCd v 6pay gt c i 1 desc Location gt 28 Chapter 6 Insbridge XML Windows Example m i 3 n LocationStateCd v AL gt lt m i 4 n SignsLimit v 2500 gt m i 6 n FullCoverageYN v N gt lc lc lt rate gt REQUEST 43 lt rate lob 125 gt lt heading gt lt program parent_id 1002 program_id 1 program_ver 1 gt lt heading gt lt c i 0 desc Policy gt m i 7 nz PaymentPlanCd v 9pay gt lt c i 1 desc Location gt m i 3 n LocationStateCd v AL gt lt m i 4 n SignsLimit v 2500 gt lt m i 6 n FullCoverageYN v N gt lc lc lt rate gt REQUEST 44 rate lob 125 gt lt heading gt lt program parent_id 1002 program_id 1 program_ver 1 gt
95. um v 674 gt c i 5 gt lt m i Dwelling_1 v 640 gt m i Dwelling_3 v 0 gt m i Dwelling_5 v 0 gt m i SEC_II Personal Liability Each Occurrence v 500000 gt m i SEC_II Medical Payments Each Person v 2000 gt Ic Ic m Node Map The m map node represents an individual attribute value pair mapped for a specific SoftRater Package hosted by SoftRater In the output case it identifies an output attribute as defined in the SoftRater Package represented by the program node and its associated value The m node s attributes are defined as follows i output identifier available by default n name description of output with AddResultDesc request option V value of output available by default The m node is always a child of a c category node and is an attribute value pair for that specific category instance see the category example rate Node Input Document The rate node is optional When the rate request is issued with the Addinputs option this node is returned in the result XML doc It includes the full input rate request document that was used to generate the rate result document Example result lob 1 policyld ABC1234 AUTO gen date 2 9 2014 1 50 31 PM gt rate policyld ABC1234 AUTO gt lt rate gt lt result gt 26 Chapter 6 Insbridge XML Windows Example Input Overrides Shopping Feature By specifying inpu
96. y Oracle Insurance Insbridge Enterprise Rating system to communicate information electronically with external and internal software systems Insbridge s rating request input XML is designed to be flexible and efficient It allows for single or multiple rate requests to be submitted via one input XML document The rate requests embedded in this single document can be targeted to multiple states and or multiple lines of business Multiple versions of a rating package also can be targeted in a single rate request document The rating request response XML is also streamlined to present all the results to the various request methods described above in a single output XML document INSBRIDGE XML REQUEST FORMAT The following is an example of an Insbridge rate request XML document rate lob 2 tracking_attribute env_def PolicyNumber XMLInput_ChangeAutoComplex_127 gt lt heading gt lt program parent_id 1 program_id 318 program_ver 1 gt lt heading gt lt c i 0 desc Policy gt m i 1086 n PackageDisclnd v gt m i 1094 nz RenewalRetentionCreditlnd v gt m i 1157 n CompanyCode v gt m i 1212 n Eff_Date v gt m i 1214 nz PrimInsuredAge v gt m i 1215 nz SeclnsuredAge v gt m i 1222 n Renewallnd v gt c i 5 desc Home gt m i 1083 n TerritoryCode v gt m i 1084 n ResidenceT ype v gt lt m i 1087 n ProtectionClass v gt m i
97. y manipulation of the Insbridge XML Request but after the XML payload has been marshaled from the integrate client to the SoftRaterEJB system stop time The stop time is the internal system tracking time after all program execution and just before the SoftRaterEJB engine closes the Insbridge Response XML document which will be marshaled back to the integrating client running time The running time is the different in Milliseconds from the start time and stop time It represents the transactional duration of the program processing the request n n NMQ A y _ UND C n U NOTE Running Time is shown in milliseconds 10 seconds Examples Single Rate Request 32 Chapter 6 Insbridge XML Windows Example See Insbridge XML Request Format and Insbridge XML Result Format Multiple Rate Requests in a Single XML Document It is possible to request several rates from a single XML document These can be rates on different lines of business across different states and or different SoftRater Package versions The simple way to do this is to combine multiple lt rate gt request nodes in one single root node and submit it for rating The root node can be anything however in the WSI call it is always lt ibdoc gt Multiple lt rate gt nodes This request XML lt ibdoc gt lt rate gt lt rate gt lt rate gt lt rate gt lt ibdoc gt

Download Pdf Manuals

Related Search

Related Contents

Sony USM128A User's Manual  ScreenBeam Mini 2 Wireless Display Receiver User Manual  User Manual - Amazon Web Services  the Warmup Tempo Thermostat user manual.  HID Identity iCLASS Proximity Embedded      Basic characteristics data • Instruction manual    Nikon D-60 User's Manual  

Copyright © All rights reserved. Failed to retrieve file