IBM Notes and Domino 9.0 Social Edition System Administration B Study Guide
This credential validates administration of IBM Domino 9.0 Social Edition across planning, installation, configuration, security, networking, replication, messaging, integration, and user management. IBM positions it for experienced Domino system administrators, while the official page now records the certification as withdrawn on November 30, 2019, with “Required exam: N/A” and “Exam status: N/A.” This guide helps you decide whether to pursue historical preparation, refresh operational knowledge, or verify a current IBM replacement before scheduling anything.
Confirm what “System Administration B” refers to before you study
The supplied catalogue label says IBM Notes and Domino 9.0 Social Edition System Administration B, but IBM’s official credential page names the certification “IBM Certified System Administrator - Notes and Domino 9.0” and shows credential code 14003306. The page also states that the certification was withdrawn on November 30, 2019, and currently displays “Required exam: N/A” and “Exam status: N/A.”
That distinction changes the first preparation decision. Do not treat an old catalogue name as proof that a live exam appointment exists. Use the official IBM page to confirm the credential’s historical identity and check IBM’s current certification information for any successor. If your objective is a qualification that can be scheduled today, investigate current options before investing in exam-specific materials.
The available official evidence does not provide a current exam number, question count, passing score, exam duration, delivery method, languages, pricing, or a live scheduling route for this credential. Those details should therefore not be inferred from third-party listings or practice-question pages. A page advertising a “System Administration B” exam may be using a catalogue taxonomy rather than IBM’s current naming.
Use the official record as the decision point
Start by opening IBM’s certification page and recording the exact title, code, status, and any successor information IBM provides. If an employer or training provider supplied the “B” designation, ask which IBM credential or historical exam it means. Request the source document rather than assuming that the label identifies an active test.
This check is particularly important for candidates who need a current badge, renewal path, or verifiable transcript. The technical subjects remain useful for Domino administration, but studying a historical blueprint is not the same as preparing for an active certification.
Understand the capability the credential was designed to validate
The certification scope covers planning, installing, setting up, and managing IBM Domino 9.0 Social Edition servers and users. It is aimed at experienced IBM Domino system administrators, not at someone beginning with general server administration. Preparation should therefore connect configuration choices to operational outcomes rather than focus only on isolated product terminology.
IBM identifies Installation, Administration, Networking and Integration, Security, Replication, Messaging, and User Management as key focus areas. The credential also includes integration points with other IBM products and understanding of OpenSocial standards. Together, these areas describe an administrator who can reason across a Domino environment instead of managing one server or one database in isolation.
A useful way to interpret the scope is to follow the lifecycle of a service. First plan the environment and install the required components. Then establish administration and security controls, connect servers and external systems, configure replication and mail routing, manage users, and troubleshoot the resulting behavior. This lifecycle is a study model, not an official exam sequence.
Translate the domains into administrator decisions
Installation asks whether the required server and supporting components are present and configured in the right order. Administration asks how the environment is operated and monitored. Networking and Integration asks how Domino communicates with surrounding systems. Security asks who can access which resources and how that access is controlled.
Replication and Messaging require topology thinking: which servers exchange data, which paths carry mail, and what happens when a connection or destination is unavailable. User Management requires consistent handling of identities, access, and operational changes. Reviewing each domain through these decisions will expose gaps more effectively than memorizing menu names.
Do not turn the domain list into seven disconnected flashcard piles. A change to a directory, server configuration, security setting, replication path, or mail route can affect another domain. When studying, write down the dependency you expect, the evidence you would inspect, and the least disruptive corrective action.
Check the prerequisite knowledge IBM expects
IBM’s recommended skills include basic troubleshooting, messaging concepts and architecture, IBM Connections and OpenSocial knowledge, composite applications, WebSphere Application Server, networking, Domino-compatible security concepts, and web application and directory servers. Treat this list as a readiness diagnostic. If several of these subjects are unfamiliar, begin with fundamentals before attempting detailed Social Edition configuration.
The recommended background is broad because Domino administration often crosses product boundaries. A server administrator may need to distinguish a Domino configuration problem from a network, directory, web, messaging, or integration problem. You do not need to assume that every adjacent product is configured identically; you do need to understand the role each system plays and where evidence would come from.
Create a two-column inventory before studying. In the first column, mark topics you can explain and troubleshoot without reference material. In the second, record topics you recognize only by name. Prioritize the second column, but keep the first available for cross-domain review. This prevents familiar Domino tasks from crowding out weaker integration or infrastructure knowledge.
Use troubleshooting questions instead of definitions alone
For each weak topic, ask five practical questions: what component is involved, what configuration controls it, what dependency must be available, what symptom would appear if it failed, and what evidence would confirm the cause? This method turns “know networking” into a usable investigation plan without relying on leaked or purported live questions.
For messaging, for example, map the participants, routing relationship, destination, and failure symptom. For security, identify the identity source, the authorization boundary, and the resource being protected. For integration, identify the external service, the Domino feature consuming it, and the configuration or credential material involved.
Build a Social Edition study track around the OpenSocial component
The Social Edition material deserves a separate study track because it is not merely a label applied to a standard Domino installation. IBM states that supplying OpenSocial features from a Domino server requires running the separate Domino Social Edition OpenSocial component installer wizard in addition to the standard Domino server installation wizard. Installation planning must therefore account for both installation activities.
IBM says the component supports iNotes Widgets and LiveText, OpenSocial 2.0 gadgets, and embedded experiences in iNotes. Study these as supported capability areas and then connect each to administration questions: what service or feature is being enabled, what server-side configuration is involved, and what user-facing function depends on it.
The official setup documentation identifies two concrete configuration activities: creating and configuring a credential-store application, and creating configuration settings documents for servers running Shindig. These are strong anchors for lab work or documentation review. Focus on the purpose and relationship of each item rather than copying a procedure without understanding what it controls.
Separate installation, setup, and administration in your notes
Make three headings in your Social Edition notes. Under Installation, record the separate OpenSocial component requirement and the point at which it fits into the server setup. Under Setup, record the credential-store application and Shindig-related configuration settings documents. Under Administration, record the supported features and the operational checks needed after configuration.
This separation helps prevent a common mistake: assuming that a successful installer run proves that every supported feature is ready for users. Installation places software on the system. Setup supplies configuration and credentials. Administration verifies that the resulting service is appropriate for the intended environment and remains manageable.
Use IBM’s installation and setup documentation as the procedural authority. If a local lab differs because of operating-system, topology, or product-version constraints, label the difference in your notes. Do not silently substitute an unrelated Social Edition or OpenSocial procedure for the version-specific material.
Study Shindig and credential handling as dependencies
IBM’s setup guidance specifically refers to servers running Shindig and to a credential-store application. Your study notes should therefore trace how a request or embedded feature depends on server configuration and credential availability. The goal is not to guess undocumented internals; it is to identify the configured objects that an administrator would inspect when an OpenSocial feature cannot operate as intended.
Document the expected relationship between the server, its configuration settings documents, the credential store, and the supported user-facing feature. Then record what you would verify after a change: the relevant configuration exists, the intended server receives it, credentials are available through the configured mechanism, and the feature is tested in its supported context.
Learn the Domino Administrator as an operational control surface
IBM describes the Domino Administrator as the administration client for Notes and Domino and says it can perform most administration tasks. IBM also states that Domino systems can be administered using either the local Domino Administrator or the Domino Web Administrator. Study the administration client as a way to perform and verify work, not as a list of interface labels.
For each major task, identify the administrative object being changed, the authority required, the scope of the change, and the evidence that confirms success. A server-wide setting, a database access change, a user action, and a replication adjustment should not be treated as equivalent operations merely because they appear in the same client.
Include the Web Administrator in your review. The official evidence confirms that both local and web administration are available, but it does not establish that every task is identical in both interfaces. Avoid memorizing an unsupported feature-by-feature equivalence. Instead, verify the task in the relevant IBM documentation and note any interface-specific limitation.
Create a repeatable administration worksheet
A useful worksheet has six fields: objective, object or server affected, prerequisite authority, configuration location, validation evidence, and rollback or recovery consideration. Complete it for representative installation, security, replication, messaging, and user-management tasks. This forces you to connect an action with its consequences.
Add a final field for scope. Ask whether the action affects one user, one database, one server, a server group, or the wider environment. Scope errors are more dangerous than simple navigation errors because an otherwise correct change can produce an unexpected result when applied to the wrong target.
Organize installation and configuration study by dependencies
Installation preparation should begin with architecture and prerequisites, then move to the base Domino server, the separate Social Edition OpenSocial component where required, server setup, and validation. This order reflects the documented distinction between the standard Domino installation wizard and the separate OpenSocial component installer wizard.
Do not begin with user-facing features before you can explain the server foundation they depend on. An administrator who knows how a gadget or embedded experience is supposed to appear but cannot identify the server component, configuration settings, or credential store has an incomplete operational model.
As you review IBM documentation, record inputs and outputs for each stage. Inputs may include installation media, server identity, configuration choices, or credentials. Outputs may include installed components, configuration documents, or an available administration surface. This makes it easier to identify where a failed result first diverged from the intended setup.
Use a clean lab or controlled documentation exercise
If you have an authorized Domino 9.0 Social Edition environment, perform changes in a controlled lab and keep a change log. Record the starting state, the action, the affected server or application, and the observed result. If you do not have a lab, build a configuration map from the IBM documentation and practice explaining the sequence aloud or on paper without claiming that a procedure has been tested.
Do not make production changes merely to create study evidence. The purpose of practice is to understand dependencies and validation, not to experiment on live users, mail routing, replication, or credentials.
Study clustering, monitoring, replication, and mail routing as topology problems
IBM identifies clustering, expanded monitoring configurations, and replication/mail-routing topologies as administration skills associated with the credential. The practical study task is to draw the environment. Show servers, databases or services, network relationships, replication paths, mail routes, monitoring responsibilities, and the user or application that depends on each path.
A topology diagram gives you a way to reason about failure. If a user cannot reach a resource, ask whether the problem is local availability, a network path, replication freshness, authorization, or a mail-routing destination. If an administrator sees inconsistent data, ask which replicas participate, what path connects them, and whether the observed copy is the expected source for that user or application.
Keep replication and mail routing separate in your diagram even when they share infrastructure. Replication concerns synchronization of Domino data between participating replicas. Mail routing concerns delivery paths and destinations. Blending the two makes troubleshooting less precise and encourages the wrong corrective action.
Make monitoring actionable
Expanded monitoring configurations should be studied as a relationship between what is monitored, where observations are collected, and how an administrator responds. Write down the signal you would inspect, the component it represents, and the next diagnostic step. “Monitor the server” is not a sufficient study note; identify the operational question the monitoring configuration is meant to answer.
For clustering, focus on service continuity and placement decisions. Ask which resource is expected to remain available, what the alternate path is, and what configuration or status information would reveal a problem. For replication, identify the expected partner and data flow. For mail routing, identify the next hop and the evidence that delivery progressed or stopped.
Treat security as a chain of identity, authority, and resource
Security preparation is stronger when every scenario is expressed as identity, authority, resource, and action. Identify who or what is requesting access, which Domino-compatible security control grants or denies it, what resource is protected, and what operation is attempted. Then ask how an administrator would confirm the effective result.
IBM’s recommended skills include Domino-compatible security concepts, and the credential’s scope includes managing servers and users. That makes identity and administrative authority central study topics rather than optional background. Review how user-management actions, server administration, database access, and integration credentials fit into the broader security model.
For Social Edition features, include the credential-store application in your security map. The official setup evidence confirms that this application is created and configured as part of setting up the OpenSocial component. Study its administrative purpose and the consequences of misconfiguration, while avoiding unsupported assumptions about credentials or security behavior not stated in the IBM documentation.
Avoid the broad-access shortcut
A frequent preparation mistake is treating broad administrative access as the default solution to every failure. That approach hides the real dependency and creates unnecessary exposure. Instead, identify the narrow authority required for the task, confirm the target, and validate the result with the least expansive test available.
When reviewing a scenario, distinguish authentication from authorization. A recognized identity does not by itself explain whether the identity can administer a server, open a database, use a feature, or access an external service. Keeping those questions separate makes both study answers and operational troubleshooting more defensible.
Connect messaging and user management to service operations
Messaging study should cover concepts and architecture, while user-management study should cover the administrative lifecycle and its effect on services. Map how an identity is represented, how access is assigned, how mail is routed, and what changes when a user or destination is altered. Keep the focus on relationships and validation rather than memorized command fragments.
IBM lists Messaging and User Management as separate focus areas, but they interact in real administration. A user change can affect access, addressing, mail delivery, directory information, and application use. Your notes should show which result belongs to which domain and which evidence would distinguish an identity problem from a routing or authorization problem.
For each user-management procedure you review, document the intended scope, prerequisites, affected resources, and post-change checks. For each messaging procedure, draw the route and identify the expected destination. This gives you a consistent way to reason about both routine work and failure scenarios.
Build two scenario sets
Create one set of scenarios for normal administration: adding or changing a user, preparing access, configuring a route, or validating a service. Create another for diagnosis: a user cannot access a resource, mail does not reach its destination, a replica is not current, or a Social Edition feature is unavailable. For each scenario, write the first three checks before writing a fix.
Do not rely on a single symptom to identify a cause. The same visible failure may arise from identity, authorization, connectivity, configuration, or service availability. A disciplined sequence of checks is more transferable than a memorized response to a narrowly worded prompt.
Use IBM documentation without turning study into passive reading
Read the certification page for scope and readiness expectations, then use the product documentation to convert each topic into an action-and-validation note. The Domino Administrator documentation grounds your understanding of administration clients, while the OpenSocial documents provide the component’s installation, setup, and supported-feature context.
After each reading session, close the page and reconstruct the process from memory: what is being configured, why it matters, what depends on it, and how you would verify it. Reopen the source to correct omissions. This active recall approach is a practical recommendation, not an IBM requirement, but it makes documentation review more useful.
Keep source notes tied to exact claims. If a page says the component supports a capability, record that support. If a page describes a setup object, record the object and its role. Do not extend a short statement into an undocumented promise about compatibility, performance, exam coverage, or delivery.
Create a source-backed knowledge map
Use the certification page as the top-level map for Installation, Administration, Networking and Integration, Security, Replication, Messaging, and User Management. Link the Domino Administrator page to administration tools. Link the OpenSocial administration page to supported features, the installation page to the separate installer requirement, and the setup page to the credential store and Shindig configuration settings documents.
Mark every note as one of three types: official requirement or scope, documented product behavior, or personal preparation recommendation. This simple labeling prevents a study tactic from being mistaken for an IBM rule and prevents a general product assumption from being presented as an exam fact.
Follow a practical four-stage roadmap
A staged roadmap works best when it moves from readiness to architecture, then configuration and troubleshooting, and finally verification. Because IBM’s official page records this credential as withdrawn and does not list a required exam, use the roadmap for historical knowledge refresh or role preparation unless IBM confirms a current successor or assessment.
Set a clear decision gate at the end of each stage. Continue when you can explain the material and apply it to a scenario; revisit the stage when you can only repeat terminology. Do not measure readiness by the number of pages read or by confidence gained from unverified practice questions.
Stage 1: Establish scope and baseline knowledge
Begin with the official title, credential code, intended audience, scope, focus areas, and recommended skills. Build your topic inventory and mark gaps in troubleshooting, messaging, networking, security, integration, OpenSocial, and adjacent server knowledge. Confirm whether your goal is historical study, operational competence, or a current certification before selecting resources.
Your output for this stage should be a one-page map of the environment and a prioritized list of weak areas. If you cannot explain how the listed domains relate to a Domino service, spend more time on fundamentals before moving to detailed configuration.
Stage 2: Model the server and service architecture
Study installation and administration first, then draw the server, database, user, network, replication, and mail relationships that support the environment. Add the Social Edition OpenSocial component as a distinct installation concern. Identify where the Domino Administrator or Domino Web Administrator fits into routine operations.
Your output should be a topology diagram and an administration worksheet. For every major object, record its purpose, dependencies, authority boundary, and validation evidence. The diagram does not need to reproduce an undocumented enterprise design; it needs to make your reasoning visible and testable.
Stage 3: Work through configuration and failure scenarios
Review security, replication, messaging, user management, networking, integration, and OpenSocial setup as connected scenarios. Include the credential-store application and Shindig-related configuration settings documents in the Social Edition track. For each scenario, identify the symptom, the first evidence to inspect, the likely dependency, and a controlled corrective action.
Your output should be a troubleshooting matrix. Keep separate rows for installation failure, configuration mismatch, access denial, replication inconsistency, mail-routing trouble, connectivity failure, and unavailable Social Edition functionality. This structure discourages one-size-fits-all answers and highlights which domain a scenario actually tests.
Stage 4: Verify competence and make the scheduling decision
Conduct a closed-book review using your own scenarios and documentation map. Explain each focus area, trace a change through its dependencies, and state how you would validate the result. Then revisit IBM’s official certification information to determine whether a current exam or successor is available. Do not schedule from a third-party listing alone.
Your final output should be a short readiness record: topics understood, topics requiring reference material, lab or documentation exercises completed, and the status of the current certification route. If the route is unavailable, retain the technical notes for work or a successor credential rather than treating historical exam preparation as a current certification plan.
Conclusion
The most important preparation step for this catalogue entry is verification, not memorization. IBM’s official record identifies the historical Notes and Domino 9.0 credential, its administration scope, recommended background, credential code 14003306, and withdrawal on November 30, 2019; it does not provide a current required exam or active exam status. Use the documented domains to build practical Domino and Social Edition knowledge, study the separate OpenSocial installation and setup dependencies, and confirm IBM’s current certification route before making a scheduling decision.
