|
Steps:
|
| |
1. Review and verify compliance with the appropriate Validation Requirements for Java Controls and/or IDE Extensions
|
| |
2. Digitally sign your control deliverable ZIP file
|
| |
3. Complete and Submit the ComponentSource / BEA Online Product Submission for Testing form
|
| |
4. Print, sign, and return fax the “BEA Workshop Validation Program Enrollment Agreement”
|
| |
5. Pay the Validation testing fee
|
| |
6. Submit the Control / Extension
|
| |
7. Receive your test results
|
| |
8. Validated Control and/or IDE Extension will be listed in the BEA Premiere Component Gallery. BEA delivers validation marketing benefits.
|
| 1. Review and verify compliance with the appropriate Validation Requirements for Java Controls and/or IDE Extensions |
|
Review the appropriate Validation Requirements form for the product you are submitting. The process differs depending upon whether you are submitting a Java Control [Read the WebLogic Controls Test Plan Overview] or a WebLogic Workshop IDE Extension [Read the WebLogic Extensions Test Plan Overview]. ComponentSource and BEA will use these requirements in determining validation for your product. You may submit beta products for testing, but they must be fully functional and feature complete.
|
| 2. Digitally sign your control deliverable ZIP file |
| WebLogic Workshop requires that the control deliverable ZIP files contain a digital signature, in order to ensure that the file has not been tampered with. Instructions for how to digitally sign your control deliverable files can be found here. |
| |
| 3. Complete and Submit the ComponentSource / BEA Online Product Submission for Testing form |
The Product Submission for Testing online form is used to submit a product for testing. It facilitates entering company information, product information - such as minimum system requirements, product features, and any other ancillary information that assists in the validation process.
|
| 4. Print, sign, and return fax the "BEA Workshop Validation Program Enrollment Agreement" |
In order to receive the BEA-Validated program benefits - including the BEA-Validated log - you are required to sign the Validation Enrollment Agreement and return it by fax to BEA. You must agree to the terms and conditions of the BEA-Validated program. You can download the form here.
|
| 5. Pay the Validation testing fee |
The fee for validation testing varies depending upon whether you are submitting a control or an IDE extension. For detailed pricing information, click here. To purchase validation testing, click here.
|
| 6. Submit the Control / Extension |
Once your Product Submission Form has been received, you will be contacted via email or telephone with instructions for rendering payment for testing. Testing will not begin until payment has been received. Additionally, you will be informed how to transmit the binary files to us. This must include all related resources required for validation, packaged in an appropriate archival file format such as .jar, .tar.gz, .zip, etc. File transmission is typically accomplished via email for files smaller than 1 MB, and via FTP for larger files.
|
| 7. Receive your test results |
Once testing is complete, you will be notified via email (unless otherwise requested) as to whether your product is certified. Validation testing typically takes 5-10 business days. If your Control / Extension passes validation, you will receive the ComponentSource / BEA validation logo requirements along with camera-ready artwork of the validation logo.
|
| 8. BEA Premiere Component Gallery Listing and Validation Marketing Benefits Begin. |
Once your Control or IDE extension has been validated, it will be listed in the BEA Premiere Component Gallery. You will also be able to take advantage of the BEA validation marketing benefits included in the program.
|
| To submit your product for BEA Validation please use the Validation Submission Form, or for more information, please contact us. |
