JITC
JOINT INTEROPERABILITY TEST COMMAND
HOME
Notice and Consent
Legal and Regulatory
ABOUT JITC
About JITC
Our Leaders
Our History
Organization
SERVICES CATALOG
RESOURCES
Registers
IBS
IBSL Register
GEOINT
Conformance
Extensions
DES
TRE
Field Value
PKE
Application Status
ECA Status
OCSP Testing Status
External PKI Testing Status
CCEB Partner PKI Testing Status
RMA
Product Register
UHF SATCOM
IBS CIB Register
IW Register
Legacy UHF SATCOM Register
Resources
IOP Steering Group (ISG) Resource Site
Labs
Projects
Tools
Rates
REFERENCES
Policies and Governance
JITC Publications
VISITOR SUPPORT
General Information
Fort Huachuca Information
Fort Meade Information
CONTACT US
JITC
JITC Webmaster
JITC PUBLIC KEY INFRASTRUCTURE (PKI)
Home
Labs
CAC
GDS
PKE
Application Testing
External Certification Authority Testing
Online Certificate Status Protocol Responder Testing
DoD PKI Interagency/Partner Interoperability Testing
DoD PKI CCEB/Partner Interoperability Testing
PKI
Obtaining Test Certificates
Obtaining Test Common Access Cards
PKI Lab Environment
Resources
Acronyms
Frequently Asked Questions
Online Resources
Terms and Definitions
Contact Us
Points of Contact
Request for Information
PUBLIC KEY ENABLED (PKE) - APPLICATION STATUS
Updated: 7/19/2021 10:10:21 AM
webMethods, Inc., Integration Platform, version 1.0
Web Site
webMethods, Inc.
Status
INITIAL - Waiting for software to be shipped.
Date Certified
N/A
Type/Supported Functions
Portal Solutions. Single Sign-On
Operating Systems Supported
Windows NT, Windows 2000, Sun Solaris, HP-UX, IBM AIX
Associated Software
WebMethods runs inside a Java Virtual Machine.
WebMethods servers require JVM 1.2.2 or above
WebMethods development environments require JVM 1.3 or above
Administration of the webMethods Integration Platform can be done through a browser based User Interface, such as Netscape or Internet Explorer.
Audit and logging information is stored in a relational database, such as Oracle, DB2, and Microsoft SQL Server.
Common Access Card Information
N/A
Application Description
Users authenticate to the webMethods Integration server using a certificate and the server uses ACLs to control access to particular services provided by the server. The webMethods Integration Server can function as a web server, thus creating a portal environment. Communication between back-end systems and the webMethods Integration server is protected depending on the protocols the back-end system supports, such as HTTP and SSL. Back-end systems may include ERP systems such as SAP R/3, Baan, PeopleSoft, Oracle applications, web servers and other legacy applications. When placed in a DMZ, the webMethods Integration Server communicates with internet users over SSL sessions then may communicate securely with the back-end systems, thus not exposing the communications between the back-end systems and the internet users.
This description was provided by the vendor.
Back to Application Status Page
Top of Page