Guidewire BillingCenter
Guidewire BillingCenter is Guidewire’s insurance billing system with prebuilt models and flexible architecture to support all existing and future policyholder transactions.
For more information about the API, see Guidewire Cloud API Documentation.
-
For more information about connecting to SaaS applications, see SaaSアプリケーションへの接続.
-
For more information about Lite connectors, see SaaS アプリケーションコネクタの分類.
-
Depending on your use case, you might need to install Data Movement gateway to move data from SaaS applications. For more information, see どのようなときに Data Movement gateway が必要ですか？.
Supported update methods
For more information, see ターゲット更新方法の概要.
Landing tasks:
-
Change data capture (CDC)
-
Reload and compare
Replication tasks:
-
Change data capture (CDC) using Change Tables
-
Full load
Landing data in a data lake tasks:
-
Change data capture (CDC)
-
Reload
Preparing for authentication
To access your Guidewire data, you need to authenticate the connection with your account credentials.
Creating the connection
For more information, see SaaSアプリケーションへの接続.
- Fill in the required connection properties.
-
Provide a name for the connection in Connection name.
-
Select Open connection metadata to define metadata for the connection when it has been created.
-
Click Create.
| Setting | Description |
|---|---|
| Data gateway |
ユース ケースに応じて Data Movement gateway を選択します。 情報メモ
Qlik Talend Cloud スターター サブスクリプションでは Data Movement gateway をサポートしていないため、この項目は使用できません。別のサブスクリプション ティアを利用しており、Data Movement gateway を使用しない場合は、 [None] (なし) を選択します。 Data Movement gateway の利点とそれを必要とするユース ケースの詳細については、「Qlik Data Gateway - データ移動」を参照してください。 |
| JWT Payload | JSON Web Token payload is a set of claims. Each claim is a key/value pair that represents information that the bearer of the token claims to be true. |
| Signing Algorithm | The algorithm to sign the JWT. |
| Private Key | The private key to sign the JWT. |
| Token URL | Token URL. |
| Token Request Body | The body to send to the Token URL. Use <signed> as a variable for the signed JWT Payload.
Example: grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<signed> |
| Base URL | The base URL for this source. This is the common part of the endpoints preceding /bc/rest/. |
| User Context | User context.
The contents of this field will be base64-encoded and included as GW-User-Context header. If a user context is not needed, leave the field empty. For more information, see JWTs for services with user context. |
Supported datasets
The following datasets are supported. For more information about the datasets, see Guidewire Cloud API Documentation.
-
Agency Bill Plans
-
Billing Plans
-
Commission Plans
-
Delinquency Plans
-
Payment Allocation Plans
-
Payment Plans
-
Return Premium Plans
-
Disbursements
-
Suspense Payments
-
Batch Processes
-
Database Consistency Checks