CONTROL-SA Connector Integration And Installation Guide
Oracle Enterprise Single Sign-onProvisioning GatewayCONTROL-SA Integration and Installation GuideRelease 10.1.4.0.3E10332-01June 2007
Oracle Enterprise Single Sign-on Provisioning Gateway CONTROL-SA Integration and Installation Guide, Release10.1.4.0.3E10332-01Copyright 2006-2007, Oracle. All rights reserved.The Programs (which include both the software and documentation) contain proprietary information; theyare provided under a license agreement containing restrictions on use and disclosure and are also protectedby copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,or decompilation of the Programs, except to the extent required to obtain interoperability with otherindependently created software or as specified by law, is prohibited.The information contained in this document is subject to change without notice. If you find any problems inthe documentation, please report them to us in writing. This document is not warranted to be error-free.Except as may be expressly permitted in your license agreement for these Programs, no part of thesePrograms may be reproduced or transmitted in any form or by any means, electronic or mechanical, for anypurpose.If the Programs are delivered to the United States Government or anyone licensing or using the Programs onbehalf of the United States Government, the following notice is applicable:U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical datadelivered to U.S. Government customers are "commercial computer software" or "commercial technical data"pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. Assuch, use, duplication, disclosure, modification, and adaptation of the Programs, including documentationand technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle licenseagreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, CommercialComputer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA94065.The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherentlydangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,redundancy and other measures to ensure the safe use of such applications if the Programs are used for suchpurposes, and we disclaim liability for any damages caused by such use of the Programs.Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or itsaffiliates. Other names may be trademarks of their respective owners.The Programs may provide links to Web sites and access to content, products, and services from thirdparties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.You bear all risks associated with the use of such content. If you choose to purchase any products or servicesfrom a third party, the relationship is directly between you and the third party. Oracle is not responsible for:(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with thethird party, including delivery of products or services and warranty obligations related to purchasedproducts or services. Oracle is not responsible for any loss or damage of any sort that you may incur fromdealing with any third party.
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideTable of ContentsIntroduction . 4Audience. 5Related Documentation . 5CONTROL-SA Connector Architecture . 6Interface. 6Installation Overview. 7System Requirements. 7Pre-Installation Checks . 7Installation Steps . 7Installation Instructions . 8Installation of new RSS Type . 8Installation of CONTROL-SA Module .10Configuration of CONTROL-SA Module .15Patch to Support Additional Java Class PATH in the SA Agent .21Copying the flat file containing ESSO-PG Users.24Un-installation of the USA–API . 25Oracle ESSO-PG USA-API Interaction . 26Agent Function List . 27Appendix . 28Resources Utilization .28Memory Usage.28Data Storage .28Protocol Security.28Messages . 28Keywords . 29RSS User Keywords .29RSS User Group Keywords.29RSS User to User Group Connection Keywords .29Glossary . 303
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideIntroductionCONTROL-SA is BMC Software’s solution that enables management of securitysystems distributed across multiple incompatible platforms. USA-API stands forUniversal Security Administration Application Programming Interface. TheUSA-API is the interface between a Resident Security System (referred to as theRSS) and SA-Agent.CONTROL-SA includes the components illustrated below, which together providecentralized security administration for the entire enterprise.The SA-Agent platform contains the following elements: One or multiple instances of the SA-Agent program. This programreceives commands from ENTERPRISE SECURITY STATION and passesthem to the correct USA-API. Messages from the USA-API are passed viaSA-Agent to ENTERPRISE SECURITY STATION. SA-Agent contains the SA-Agent gateway. Using a TCP/IP or an SNALU6.2 link, this module connects the SA-Agent platform to theENTERPRISE SECURITY STATION workstation and enables communication. One or more USA-APIs. Each USA-API is an interface that is designed tocommunicate with a specific type of RSS.The Resident Security System (RSS) is a security product or module. The RSS maybe the native security of an operating system (e.g., Solaris, HP-UX, Novell NetWare)or any other product that implements security (e.g., RACF, Sybase, SeOS). While theRSS may reside anywhere in the network, it is managed via the SA-Agent platform.4
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideEach RSS has its own RSS database containing security administration data for theRSS.Interaction between SA-Agent and the RSS is achieved through the USA-API. Sinceeach RSS has different facilities and operates using its own unique terminology, SAAgent is provided with a dedicated USA-API for each type of RSS supported. The useof dedicated USA-API’s enables SA-Agent to handle the unique features andoperations of each RSS.USA-API works as communicator between CONTROL-SA & the Resident SecuritySystem (RSS). It takes inputs from CONTROL-SA, and formats them into messagesthat are understood by Oracle Enterprise Single Sign-on Provisioning Gateway(ESSO-PG). In turn it interprets the results from Oracle ESSO-PG and formats theresults into a form that is understood by CONTROL-SA.USA–API interacts with Oracle ESSO-PG using the CLI provided by Oracle and theuser file which has the user information.The CONTROL-SA Connector manages the following: EntitiesUsers, User to User Group Connections(Credentials) AttributesThese are keywords related to User, User Group, and User to User GroupConnections.AudienceThis guide is intended for administrators who either install or configure the USA-APIsfor CONTROL-SA. This guide describes concepts and tools required by theadministrator for setting up and administering the CONTROL-SA Connector.Users of this guide should have knowledge of the following: CONTROL-SA Functionality CONTROL-SA ESS Server configuration CONTROL-SA Agent Functioning of USA-APIRelated DocumentationThis guide refers the following documentation:5 CONTROL-SA: Getting Started Guide Version 3.1.00 Enterprise Security Station User Guide (Windows GUI) Version 3.2.00 USA- API Design and Implementation Guide Version 3.1.05
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideCONTROL-SA Connector ArchitectureThe CONTROL-SA Connector is designed to manage the Oracle ESSO-PG repositoryand is configured on a W2K platform with CONTROL-SA Agent for W2K installed.InterfaceThe following explains the communication mechanism between USA-API and SAAgent and USA-API and Oracle ESSO-PG.Interface with the SA-AgentUSA–API receives the inputs as function parameters from SA-Agent. Resultsare returned as return values from functions. Additional values are updatedinto the addresses passed as function parameters. Refer Chapter 13 of theUSA-API Design and Implementation Guide for more details which explains alldata types, which are used between SA-Agent & USA- APIs.Interface with Oracle ESSO-PG repositoryThe Get functions for User Group and User to User Group Connection and theSet functions of the CONTROL-SA Connector application are implementedusing the CLI provided by Oracle and the Get function for Users has beenimplemented using the user file, which has the user information.6
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideInstallation OverviewThis provides required information and step-by-step instructions for installing theCONTROL-SA Connector.Before running the installation procedure, it is recommended that you review theinformation in this section to ensure that the installation procedure runs smoothlyand successfully.System RequirementsInstalling and operating CONTROL-SA Connector requires the following:Operating SystemWindows 2000 ServerSoftwareOracle ESSO-PGMemory256 MB RAMDisk Space10 MB free disk space (preferably in the local drive)Installation DeviceCD-ROM drivePre-Installation ChecksThe following should be performed before installing the Connector: Determine the name of the RSS to be managed by the CONTROL-SAConnector as mentioned in the ESS GUI RSS Window. Default admin should be a dummy account and it should be addedthrough ESS GUI.Installation StepsInstallation of the CONTROL-SA Connector consists of the following steps: Install new RSS Type Installation Of CONTROL-SA Module Configuration of CONTROL-SA Module Application of the Patch to Support Additional Java Class PATH in theCONTROL-SA Agent Copy the ASCII flat file containing ESSO-PG UsersRSS parameters must be configured for each RSS to be managed via the SA-Agentplatform.7
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideInstallation InstructionsThis section describes how to install the CONTROL-SA Connector and integrate it intothe SIM workflow.Installation of new RSS TypeThe CONTROL-SA Agent for Oracle package contains a file:ManagedSystem Passlogix.shThis script adds support for your Managed System type in Enterprise SecurityStation.It is used in defining the new Managed System Type Entity and the new user-definedKeywords in the ESS database.To import a new Managed System type and keywords into ESS, or to modifyexisting Keywords:1. Log in to the Enterprise SecurityStation workstation as the ESS owner.2. Copy the script ManagedSystem Passlogix.sh from the deploymentmodule directory (\Program Files\EagleEye\SAAgent\DATA\USAAPI\Passlogix) to the ESS home directory.3. Enter the following command to change the file permissions and change toa tcsh shell:chmod 500 ManagedSystem Passlogix.shtcsh4. Run the ManagedSystem Passlogix.sh script. You are requested toprovide the name and password for an ESS administrator.5. Enter the name and password of an ESS administrator who has sufficientaccess rights to modify Managed System and ESS keywords information inEnterprise SecurityStation.6. On a Microsoft Windows computer where ESS Console is installed:a. From the Start menu, select Programs EnterpriseSecurityStation Managed System Type Activation. The Logindialog box is displayed.b. Specify the ESS log in name and password of an ESS administratorwho is defined as a Superuser. Select the relevant EnterpriseSecurityStation Login Profile. Click OK.The Managed System Type Activation window is displayed:8
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guidec. Ensure that the new Managed System type appears in the ActiveManaged System Types list.d. Click Apply to save your changes to the Enterprise SecurityStationdatabase. The window remains open while the changes are saved. Theprocess of saving the changes to the database may require severalminutes. Upon completion, a message box is displayed, reminding youto stop and restart Orbix, Gateway, and ESS Console processes.e. Click OK to close the message box.f.9Click Done to close the window.
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideInstallation of CONTROL-SA Module1. Login to the machine and insert the CD into the CD-ROM drive.2. Double click the setup.exe file, which will be available on subdirectorySetup/win.3. Click Next to start the installation.10
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide4. Click Yes to accept the license agreement.5. Select the installation path, or accept the default path. Click Next.11
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide6. Select the Encrypted option for secure communication. Click Next.7. Enter host name or IP Address of the system. Click Next.12
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide8. Enter the TCP/IP Port Number to be used for data transmission. ClickNext.9. Click Next.13
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide10. Click Next and wait for sometime.11. This is the final window of the installation. Click Yes and continue theconfiguration procedure. Please see the next section for instructions.Otherwise click No to terminate the procedure14
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideConfiguration of CONTROL-SA Module1. The Start menu on the Windows task bar contains a separate entry foreach Instance ID, in the format SA-AgentInstanceId. For example, toconfigure the instance whose instance ID is New, you would select thefollowing from the Start menu: Programs CONTROL-SA SAAgent Add Managed System.2. Enter the Oracle Managed System name.3. Enter the Managed System description.15
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide4. Enter the default administrator account name for the SA Agent. Anyaccount that has access rights to the v-go-pm-users.dat file can be usedhere.5.16Enter the default administrator password.
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide6. Enter the Offline Interceptor execution interval. This interval’sfunction is to check the v-go-pm-users.dat file for new users at thegiven interval.Note: This interval must be entered in the (HHMMSS) format. Forinstance, the a value of “010000” would equal 1 hour.7. Enter the v-GO Web Service URL.17
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide8. Enter the Username to authenticate against the Web Service.9. Enter the Password to authenticate against the Web Service.18
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide10. Enter the Identifier for this agent.11. Press C to Confirm the entries; otherwise press R for Retry or A to Abortthe current values.19
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide12. Enter Y to Start the agent or N to Restart later.13. Click Finish to complete the installation.20
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuidePatch to Support Additional Java Class PATH in the SA AgentThis patch is located in the Patch/PAXAG.3.6.02.002 directory.PAXAG.3.6.02.002: Support Additional Java Class PATHSummary This patch provides support for additional class path for Javaconnectors.Note: This step is mandatory.Affected Product CONTROL-SA/XModule Studio version 3.6.02(for both Solaris and Microsoft Windows)Files in this patch XSA LangJava.so - the shared object which implements the fix(Solaris version)XSA LangJava.dll - the dll which implements the fix (Windowsversion)JavaLibPath.txt - sample classpath file with a sample unix class pathProblem description The Java engine module did not have a mechanism to receiveadditional class path.This problem has been resolved by updating the Java controllershared/dll object (XSA LangJava.so/dll) that is responsible forloading the JVM.The classpath is controlled by a new configuration file namedJavaLibPath.txt.The path to the Java CLI (pmcli.jar and all supporting files) must beadded to the JavaLibPath.txt file. Each .jar file entry must beseparated by a semicolon on Windows and a colon on Unix. Add thefollowing to the JavaLibPath.txt file (each on separate lines forclarity): path \PMCLI.jar; path \activation.jar; path \axis-1.2.1.jar; path \bcprov-jdk13-128.jar; path \commons-discovery-0.2.jar; path \commons-logging-1.0.4.jar; path \jaxrpc.jar; path \log4j-1.2.9.jar; path \mail.jar;21
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation Guide path \opensaml-1.0.1.jar; path \saaj.jar; path \wsdl4j-1.5.1.jar; path \wss4j.jar; path \xmlsec-1.2.1.jar;Replace path with the full path to the jar file and place each entryon one unbroken line.The Java CLI also requires that the following files be placed in theendorsed directory of the Java CLI installation folder(%JAVA n.jarxercesImpl.jar22
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideTo install the patch for Microsoft Windows Note: This step is mandatory.1.Back up XSA LangJava.dll (located in the SA-Agent EXEdirectory).2. The Patch can be found in the following directory: Passlogix Agent Directory /PAXAG.3.6.02.0023.Unpack the file PAXAG.3.6.02.002.zip in a temporary directory.This file contains the following files:- XSA LangJava.so- XSA LangJava.dll- JavaLibPath.txt4.Copy the new XSA LangJava.dll to the EXE directory.5.Do the following:a.Copy the file JavaLibPath.txt to the saAgentHome \DATAdirectory.For example, if the sample connector TDB JAVA was installed under:C:\Program Files\EagleEye\SA-Agent\the file location should be:C:\Program Files\EagleEye\SA-Agent\DATA\JavaLibPath.txtb.Open JavaLibPath.txt in a text editor; replace the sampleclasspath with the appropriate classpath. Reminder - the pathseparator in Windows is ';'If the JavaLibPath.txt file does not exist or is empty - noadditional “classpath” will be used.c.23Save the file.
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideCopying the flat file containing ESSO-PG UsersNote: It is mandatory that the users are entered in this file. This is the filethat the SA agent checks at the given interval defined in Step 6 on Page 17.The filename of the ASCII flat file should be:v-go-pm-users.datIt should be placed in the following folder: SA-Agent-Installation-Directory \WORK\Passlogixwhere SA-Agent-Installation-Directory - is the SA Agent InstallationDirectory.For example: The contents of the ASCII flat file should be:User1User2User3User4.User n whereUser1, User2, ,User n - are the SSO User IDsNote: Every line should contain only one user. Please don’t leave any blanklines between users.24
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideUn-installation of the USA–APISA-Agent can be uninstalled using the Add/Remove Programs facility in theWindows Control Panel.If more than one instance of SA-Agent exists, you are given the option of uninstallinga selected instance without affecting other instances.1. From the Windows Start menu, select Settings Control Panel Add/Remove Programs.2. In the list of installed programs, select SA-Agent; then clickAdd/Remove.3. If more than one instance of SA-Agent exists, you can choose betweenremoving one instance or all instances of SA-Agent.Note:It is highly recommended that you close all active Windows applications beforestarting the uninstall procedure.If you chose to remove one instance of SA-Agent, in the next window, select theinstance ID to be removed.Upon completion, the message The deletion completed successfully is displayed.25
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideOracle ESSO-PG USA-API InteractionThe USA–API is designed to interact with Oracle ESSO-PG and update or retrieveinformation from it. These activities are performed for the following functions.1. User definitions.2. User Group definitions.3. User to User Group Connection definitions.26
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideAgent Function ListNames and descriptions of agent functions are listed below according to entity typeor function.RSS User FunctionsAccountGetAccountDeleteUser Group FunctionsGroupGetUser to User GroupConnection eConnectionDelete27DescriptionRetrieves RSS User dataDeletes RSS UserDescriptionRetrieves user group detailsDescriptionRetrieves user to user group connectiondetailsAdds a new connectionUpdates an existing connection.Deletes a connection.
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideAppendixResources UtilizationThe USA-API utilizes the following system resources during its execution: Memory CPUThe USA-API modules free the resources during termination.Memory UsageThe memory usage depends on the amount of data being downloaded during theexecution of GET functions. During the download, the maximum memory usageranges from 15-20 MB. (This estimate is for 20 users, 10 groups and 15connections.)During the execution of SET functions, the maximum memory usage ranges from 35 MB.Data StorageThe USA –API for Oracle ESSO-PG uses the standard Agent messaging facility as wellas the CONTROL-SA logging facility. These logs should be cleaned up at regularintervals. Automatic log maintenance facility of the agent can be used. Refer Section7, Page 7-32 in the CONTROL-SA Agent for Windows 2000 – Administrator Guide fordetails on how to implement Automatic Log Maintenance.Protocol SecurityThe client communicates to the server using the standard TCP/IP protocol with SSLEncryption.MessagesThe USA-API is designed to write messages during execution of the functions into thelog files. These log files can be found in the SA Agent\Log Directory.28
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideKeywordsRSS User KeywordsRSS User Functionsgu Get usersdu Delete userNoneRSS User Group KeywordsRSS User Group Functionsgug Get user groupsNoneRSS User to User Group Connection KeywordsRSS User Group Functionsgug Get user to user group connectionsauug Add user to User Group Connectionuuug Update to User Group Connectionduug Delete to User Group ConnectionESSO-PG ParametersInternal FieldNamesso descriptionsso app useridsso passwordsso other1sso 32xxxxxxx323232xxxmxxxxxxxxGUI Field labelTLenSSO DescriptionSSO ApplicationUseridSSO PasswordSSO Other1SSO Other2CCCCCMandatory keywordOptional keywordData Type of the input accepted in the field (C-Char; F-Flag; N-Integer)Length of the field
Oracle Enterprise Single Sign-On Provisioning Gateway CONTROL-SA ConnectorIntegration and Installation GuideGlossaryAPIApplication Programming Interface. The interface that translatesthe ESS commands to the native commands of application to bemanaged using CONTROL-SA.CONTROL-SACONTROL-SA is an integrated client/server solution, includingENTERPRISE SECURITY STATION and SA-Agent running onmultiple platforms throughout your organizationEntityGUIRSSAn entity defines a component used for security administration byENTERPRISE SECURITY STATION. For example, enterprise users,and user groups.Graphical User Interface. The ENTERPRISE SECURITY STATIONGUI provides operator access to the facilities and windows ofENTERPRISE SECURITY STATION through a simple graphical tool.The resident security system (RSS) is a security product ormodule. The RSS may be the native security of an operatingsystem (e.g., Solaris, HP-UX, Novell NetWare), an add-onsecurity product (e.g., RACF, SeOS), or any other product Thatrequires user registration (e.g., Sybase, Oracle).RSSAdministratorEntity that describes an administrator in an RSS. The USA-APIactions on the native system are executed in the RSS using thelogin ID of the RSS administrator.DefaultAdministratorEntity that describes the administrator for performing ReadOperations on the RSS.SA-AgentSecurity administration agent running on platforms administeredby ENTERPRISE SECURITY STATION.PlatformSA-AgentQueue30Platform on which SA-Agent runs. This platform contains theUSA–API’s for each type of RSS managed by ENTERPRISESECURITY STATION via the platform.File on the SA-Agent platform in which security events (e.g.,definition of new user) are recorded. These events aretransmitted to ENTERPRISE SECURITY STATION.If communication with the ESS gateway is temporarilyinterrupted, the events are accumulated in the queue untilcommunication is restored.
user file which has the user information. The CONTROL-SA Connector manages the following: Entities Users, User to User Group Connections(Credentials) Attributes These are keywords related to User, User Group, and User to User Group Connections. Audience This guide is intended for administrators who either .
Figure 2. Rear view 1 Optional connector 2 2 1 3 Security-lock slot 4 Wi-Fi antenna slot 5 Ethernet connector 6 USB 3.1 Gen 2 connectors (2) 7 USB 3.1 Gen 1 connector 8 HDMI 1.4 out connector 9 USB 3.1 Gen 1 connector 10 DisplayPort 1.2 out connector 11 Power adapter connector 1 Optional connector 2 Depending on the computer model, the connector might vary.
Rear panel components Figure 1-3 Rear panel components Table 1-3 Rear panel components Item Symbol Description Item Symbol Description 1 Power cord connector 10 Graphics adapter 2 Built In Self Test (BIST) LED 11 Audio line-in connector 3 Keyboard connector 12 RJ-45 network connector 4 Serial connector 13 Parallel connector 5 USB 2.0 ports 14 Mouse connector 6 IEEE-1394a connector 15 Cable .
Configure vCloud Connector Server 29 Install vCloud Connector Nodes 32 Register vCloud Connector Nodes with Clouds 43 Configure vCloud Connector Nodes 44 Register vCloud Connector Nodes with vCloud Connector Server 49 Register the vCloud Connector UI 50 4 Entering the License Key for vCloud C
GNDU connector. The back of each connector is designed for soldering. Keysight 16495D Full size connector plate for multiplexer The 16495D has twelve 8-channel shielded coaxial connectors, an Intlk connector, and a GNDU connector. The back of each connector is designed for soldering. Keysight 16495F Half size connector plate for matrix
(ISOL) IMB (Intelligent Management Bus) connector P. BMC write enable jumper Q. Jumper block R. Jumper block S. Fan connector 1 T. Server monitor module (SMM) connector U. Ultra Wide SCSI connector V. External Wake on LAN† connector W. Ultra2/LVDS SCSI connector X. Hard drive LED connector Y. Adaptec ARO-1130U2 RAIDport III connector/PCI slot 4
Network Adapter Connector 12 eSATA Connector 6 Network Activity Light 13 DisplayPort Connector 7 Wireless Network Adapter (optional) 14 PS/2 Keyboard Connector MINI TOWER COMPUTER (MT) VIEW (CONT.) SYSTEM BOARD 1 Wireless Card Connector 12 SATA Drive Connectors (4) 2 Thermal Sensor Connector 13 Internal USB Flex Bay Connector 3 Internal Speaker
1.1 Introduction to the SAP SuccessFactors Connector 1-1 1.2 Certified Components for the SAP SuccessFactors Connector 1-2 1.3 Certified Languages for the SAP SuccessFactors Connector 1-2 1.4 Architecture of the SAP SuccessFactors Connector 1-3 1.5 Use Cases Supported by the Connector 1-5 1.6 Features of the SAP SuccessFactors Connector 1-5
See the diagram on page 6. The camera system uses a 3.5 mm TRS audio connector for the Far Audio Reference input and a DSP or Phoenix connector. The TRS connector consists of the sleeve/common (section of the connector post closest to the base), the ring/right (in the middle of the connector post), and the tip/left (at the end of the connector .
