Web BLOB Configuration
WBS Kuiper Group Build (Production)
First Kuiper Group: | Name | Kuiper PRD | | Allow this group to modify Chronicles settings? |
✓ | | Application pool user | VHG\WBSServiceAccount | | Application pool user password |
2RunWBS! | | Load Balanced hostname | WBSLBprd.VHG.org | | Load Balanced hostname
for Read-Only | (blank) | | Enable requiring HTTPS functionality in IIS | ✓ | | Environments |
PRD | | Name of one server in this group | VHGWBS01 | | Number of servers in this group | 2
|
Second Kuiper Group: | Name | Kuiper SUP | | Allow this group to modify Chronicles
settings? | ✓ | | Application pool user | VHG\WBSServiceAccount | | Application pool user
password | 2RunWBS! | | Load Balanced hostname | WBSLBsup.VHG.org | | Load Balanced
hostname for Read-Only | (blank) | | Enable requiring HTTPS functionality in IIS | ✓ | |
Environments | SUP | | Name of one server in this group | VHGWBS01 | | Number of servers
in this group | 2 |
WBS Paths
Configuration for: PRD | Root Path: | \\PRDNAS\BlobRoot\PRD\ | | Configured Path 1: |
\\PRDNAS\BlobRoot\PRD\ | | Configured Path 2: | (blank) | | Configured Path 3: | (blank) | |
Failover Path: | \\AuxillaryNAS\Failover\ | | Failover Username: |
VHG\FailoverStoreAccount | | Failover Password: | 2SaveFailover! | | Failover Domain: |
(blank) | | Notifications Email: | | | Duplicate Path: | (blank) | |
Reporting Path: | (blank) | | Redundancy Path: | (blank) |
Configuration for: SUP | Root Path: | \\PRDNAS\BlobRoot\SUP\ | | Configured Path 1: |
\\PRDNAS\BlobRoot\SUP\ | | Configured Path 2: | (blank) | | Configured Path 3: | (blank) | |
Failover Path: | \\AuxillaryNAS\Failover\ | | Failover Username: |
VHG\FailoverStoreAccount | | Failover Password: | 2SaveFailover! | | Failover Domain: |
(blank) | | Notifications Email: | | | Duplicate Path: | (blank) | |
Reporting Path: | (blank) | | Redundancy Path: | (blank) |
The Flow of Web BLOB - Successful Transaction
1. Hyperspace makes a request to save a file via Web BLOB
2. The Web BLOB service routes the request to the appropriate environment
, 3. The Web BLOB service validates the file type is allowed
4. The Web BLOB service checks the size of the file
5. The Web BLOB service attempts to save the file to the primary store
6. The Web BLOB service records the file in the Web BLOB database
7. The Web BLOB service sends a success response to Hyperspace
8. Hyperspace displays confirmation to the user
9. Everything BELOW this item is unused in the process
10. The Web BLOB service fails to save the file
11. The Web BLOB service attempts to save to the failover store
During which steps are the following logs first updated?
• IIS Logs: Step 1
• Transaction Logs: Step 6
Failed Transaction
When will the Web BLOB failover store be used? List the necessary conditions:
1. The primary store is unavailable
2. The failover store is properly configured with valid credentials
3. The failover path is accessible
4. The primary store returned an error when attempting to save the file
Updating Web BLOB
1. Deploy the new environment code to SUP using Mission Control
2. Verify the environment code works in SUP
3. Deploy the Web BLOB code to SUP using Mission Control
4. Verify the Web BLOB code works in SUP
5. Deploy the environment code to PRD using Mission Control
6. Deploy the Web BLOB code to PRD using Mission Control
7. Verify the Web BLOB code works in PRD
8. Everything BELOW this item is unused in the process
9. Deploy the Web BLOB code directly to each server
10. Restart each server individually
11. Reconfigure the Web BLOB Kuiper Group
Printing Configuration
Configure EPS Routing Rules
Large Jobs Rule: | Rule Name: Large Jobs | Max CPU time in minutes: 240 | | Allowed Job
Size: 100 to (blank) | Max inactivity time in minutes: 15 | | Allowed format: All Formats | |
Fax Jobs Rule: | Rule Name: Fax | Max CPU time in minutes: 180 | | Allowed Job Size:
(blank) to (blank) | Max inactivity time in minutes: 15 | | Allowed format: InterFAX | |
For your Production EPS group, indicate the order of your EPS routing rules:
WBS Kuiper Group Build (Production)
First Kuiper Group: | Name | Kuiper PRD | | Allow this group to modify Chronicles settings? |
✓ | | Application pool user | VHG\WBSServiceAccount | | Application pool user password |
2RunWBS! | | Load Balanced hostname | WBSLBprd.VHG.org | | Load Balanced hostname
for Read-Only | (blank) | | Enable requiring HTTPS functionality in IIS | ✓ | | Environments |
PRD | | Name of one server in this group | VHGWBS01 | | Number of servers in this group | 2
|
Second Kuiper Group: | Name | Kuiper SUP | | Allow this group to modify Chronicles
settings? | ✓ | | Application pool user | VHG\WBSServiceAccount | | Application pool user
password | 2RunWBS! | | Load Balanced hostname | WBSLBsup.VHG.org | | Load Balanced
hostname for Read-Only | (blank) | | Enable requiring HTTPS functionality in IIS | ✓ | |
Environments | SUP | | Name of one server in this group | VHGWBS01 | | Number of servers
in this group | 2 |
WBS Paths
Configuration for: PRD | Root Path: | \\PRDNAS\BlobRoot\PRD\ | | Configured Path 1: |
\\PRDNAS\BlobRoot\PRD\ | | Configured Path 2: | (blank) | | Configured Path 3: | (blank) | |
Failover Path: | \\AuxillaryNAS\Failover\ | | Failover Username: |
VHG\FailoverStoreAccount | | Failover Password: | 2SaveFailover! | | Failover Domain: |
(blank) | | Notifications Email: | | | Duplicate Path: | (blank) | |
Reporting Path: | (blank) | | Redundancy Path: | (blank) |
Configuration for: SUP | Root Path: | \\PRDNAS\BlobRoot\SUP\ | | Configured Path 1: |
\\PRDNAS\BlobRoot\SUP\ | | Configured Path 2: | (blank) | | Configured Path 3: | (blank) | |
Failover Path: | \\AuxillaryNAS\Failover\ | | Failover Username: |
VHG\FailoverStoreAccount | | Failover Password: | 2SaveFailover! | | Failover Domain: |
(blank) | | Notifications Email: | | | Duplicate Path: | (blank) | |
Reporting Path: | (blank) | | Redundancy Path: | (blank) |
The Flow of Web BLOB - Successful Transaction
1. Hyperspace makes a request to save a file via Web BLOB
2. The Web BLOB service routes the request to the appropriate environment
, 3. The Web BLOB service validates the file type is allowed
4. The Web BLOB service checks the size of the file
5. The Web BLOB service attempts to save the file to the primary store
6. The Web BLOB service records the file in the Web BLOB database
7. The Web BLOB service sends a success response to Hyperspace
8. Hyperspace displays confirmation to the user
9. Everything BELOW this item is unused in the process
10. The Web BLOB service fails to save the file
11. The Web BLOB service attempts to save to the failover store
During which steps are the following logs first updated?
• IIS Logs: Step 1
• Transaction Logs: Step 6
Failed Transaction
When will the Web BLOB failover store be used? List the necessary conditions:
1. The primary store is unavailable
2. The failover store is properly configured with valid credentials
3. The failover path is accessible
4. The primary store returned an error when attempting to save the file
Updating Web BLOB
1. Deploy the new environment code to SUP using Mission Control
2. Verify the environment code works in SUP
3. Deploy the Web BLOB code to SUP using Mission Control
4. Verify the Web BLOB code works in SUP
5. Deploy the environment code to PRD using Mission Control
6. Deploy the Web BLOB code to PRD using Mission Control
7. Verify the Web BLOB code works in PRD
8. Everything BELOW this item is unused in the process
9. Deploy the Web BLOB code directly to each server
10. Restart each server individually
11. Reconfigure the Web BLOB Kuiper Group
Printing Configuration
Configure EPS Routing Rules
Large Jobs Rule: | Rule Name: Large Jobs | Max CPU time in minutes: 240 | | Allowed Job
Size: 100 to (blank) | Max inactivity time in minutes: 15 | | Allowed format: All Formats | |
Fax Jobs Rule: | Rule Name: Fax | Max CPU time in minutes: 180 | | Allowed Job Size:
(blank) to (blank) | Max inactivity time in minutes: 15 | | Allowed format: InterFAX | |
For your Production EPS group, indicate the order of your EPS routing rules:
