Download ECSA101/ ECSA 101 Hyperspace Chapter and more Exams Marketing Business-to-business (B2B) in PDF only on Docsity!
ECSA101/ ECSA 101 Hyperspace Chapter
1,2,3 & 4 | Questions and Verified Answers|
100% Correct ( New 2024/ 2025 Update )
QUESTION
How is trust established between an Epic client and the Epic operational database environment?
Answer: You define a fixed key on the client, usually in some type of environment file, and import it into Epic operational database environments.
QUESTION
What documents should you reference prior to building a new Epic client?
Answer:
- Epic 2018+ Target Platform Roadmap
- Relevant Build Checklist
- Relevant Setup and Support Guides
- Also reach out to your Client Systems representatives to discuss your plans.
QUESTION
If you were to update an Epic client before a given Epic environment, would the client be able to connect to this older environment?
Answer: Possibly. If the update to the client introduced new client-to-server dependencies; then no, the client would not be able to connect. If the update to the client did not introduce new client- toserver dependencies; then yes, the client would be able to connect.
QUESTION
What version does 85.0.47 represent?
Answer: The digits before the first decimal represent the release, in this case August 2018. The digit after the first decimal and before the second decimal represents the Interim Update, in this case there is no IU as August 2018 has no IUs. The digits after the second decimal represent the package, in this case package number 47. A package is a collection of Special Updates.
QUESTION
Which of the following is always true about dependencies? Choose one.
Answer: A. [Incorrect] A newer client will ALWAYS have unmet dependencies on the server. B. [Incorrect] A newer server will ALWAYS have unmet dependencies on the client. C. [Correct] A newer client will SOMETIMES have unmet dependencies on the server. D. [Incorrect] A newer server will SOMETIMES have unmet dependencies on the client
QUESTION
Sherlock
Answer: A tool can help you track the status of an investigation and share information between all teams involved?
QUESTION
USER WEB FORUM
Answer:
- Allows you to participate in discussions with your colleagues from other organizations.
- Keeps you up to date by reviewing the latest EPIC announcements.
QUESTION
XGM ARCHIVES
Answer: Provides access to past XGM System Roundtable or SRT presentations
QUESTION
Galaxy
Answer: One stop documentation stop. Includes Build Checklists, Target Platforms, Technical KB Articles. Allows organization of your favorite documents within your UserWeb profile.
QUESTION
Nova
Answer: EPIC's release note review tool. Review release notes for upgrades or special updates. Nova also provides information regarding the honor roll checklist and deadlines.
QUESTION
Sherlock
Answer:
Used by the the customer and EPIC to track Support Logs (SLGs), Sign Release Authorizations (RA's) and review reportable issues. Newer versions also provide checklists that track major projects, such as server builds and EPIC upgrades.
QUESTION
Client Server Infrastructure
Answer: The EPIC DB is a single database. It is referred to as an EPIC Operation Database Environment or simply just Environment. Hyperspace Clients are installed on workstations, virtual desktops and Windows Servers. Clients connect to the EPIC operation database
QUESTION
Who am I?
Answer: You must identify a Workstation Record, or LWS record, for a connection to be successful. This LWS record can be specific to the machine establishing the connection, a generic LWS, or a record shared by several connections depending on the type of client. ECSAs define a Client or Workstation ID to identify which LWS record a client should use. This ID answers the question.......
QUESTION
Where am I going?
Answer: You must define destination environments for each client. You must provide details such as the host name of the server running the Epic operational database and the TCP port the environment uses. You can define connection information for all your environments within the same environment file. This environment connection information answers the question;
QUESTION
QUESTION
True or False? Hyperspace Web is independent of Hyperspace.
Answer: False. Users access Hyperspace Web from within Hyperspace. Issues with Hyperspace can impact Hyperspace Web.
QUESTION
EPIC Releases
Answer: The Epic release is our primary versioning scheme and will contain the most significant changes. Starting with the August 2018 release, Epic is switching to a new release strategy. With this new strategy, Epic will create a new release approximately every three months. Most Epic clients on one release cannot connect to an Epic operational database environment on another release. Epic 2017 = Release 83 Epic 2018 = Release 84 August 2018 = Release 85 We recommend that you install Epic releases in your production environments every three months.
QUESTION
EPIC Special Updates or SU's
Answer: As with any software, updates are necessary to fix issues, improve existing workflows, or introduce new functionality. These SUs are a lot like hotfixes. Each SU is specific to a given Epic release and is either a client update or a server update. Client Update CXX##### - Where XX is the Release number, and ##### is a unique update ID Server Update EXX##### - Where XX is the Release number, and ##### is a unique update ID
QUESTION
Release Authorizations
Answer: Actions that change your build should follow your internal change control procedures and policies. Any change made by Epic requires a _____________. There are two types of________________; those associated with delivery of new code, and those associated with changes made by Epic personnel.
QUESTION
Dependency
Answer: when a piece of code installed in one location requires a corresponding piece of code in another. Within an Epic release, an Epic client can depend on the Epic operational database environment, but never the other way around. Individual SUs for a client can even depend on other client SUs, even across multiple clients. Client code can, but doesn't always, depend on the server code. The newer client cannot connect to the older code in the environment if there is a missing dependency. Not all client Special Updates introduce a dependency on the server. These dependencies drive the order of operations for patching and upgrading your Epic infrastructure.
QUESTION
If an Epic client is running August 2018, could it connect to an environment running August 2018 update package 23?
Answer: Yes, a client can always connect to an environment on the same release that is more up to date.
QUESTION
Could an Epic client running August 2018 update package 15 connect to an environment running August 2018?
Answer:
QUESTION
Transitional Platforms
Answer: Transitional Platforms are platforms that were previously Target Platforms. Community members can continue to use a Transitional Platform for a limited period of time. This helps provide clean upgrade paths from a previous Epic release. Separating platform upgrades from Epic upgrades reduces the risk associated with each. Transitional platforms have an end date, after which they become Off-Target platforms.
QUESTION
Exploratory Platforms
Answer: An Exploratory Platform is a platform EPIC is testing to determine whether it can become a Target Platform. Not all Exploratory Platforms will become Target Platforms.
QUESTION
Off-Target Platforms
Answer: An Off-Target Platform is any platform that does not qualify as a Target, Transitional, or Exploratory Platform. You will continue to receive support from us if you choose to go off- target. Using an Off Target Platform diminishes our ability to ensure top notch performance. We will work with you and your business leadership to ensure you understand the risks of using an Off-Target Platform.
QUESTION
Incompatible platforms
Answer:
Some platforms are more than just off-target, they are incompatible. In these cases we will still provide your personnel support. However, the software will not work properly or at all.
QUESTION
Build Checklists
Answer: These documents include a multitude of build recommendations that Epic has vetted. These checklist items often address issues found at other organizations running Epic. Checklists are available on Galaxy.
QUESTION
EPIC.Support PowerShell Scripts
Answer: We have the Epic.Support PowerShell scripts to aid you as you review your servers for build checklist compliance. You will use the Epic.Support PowerShell scripts to review Build Checklist compliance. The scripts cannot automate the entire review process as some items cannot be programmatically reviewed. After you have gone through the checklist, use the scripts to identify any missed steps
QUESTION
Hardware Configuration Guide
Answer: Guides to provide preliminary sizing for your servers along with an estimate of your storage needs. This document also provides information on the RAM and CPU you'll need for each of these servers. We base the sizing in these guides on information provided by your organization.
QUESTION
%CLIENTNAME%
QUESTION
Release
Answer: EPIC's primary versioning scheme
QUESTION
Interim Update
Answer: Collection of updates, similar to a service pack. No longer used.
QUESTION
Special Update
Answer: Fix or minor enhancement, similar to a hotfix.
QUESTION
Release Authorization
Answer: Grants Epic permission to change your system
QUESTION
SU-EEDS
Answer: Where you would download code associated with your Release Authorization (RA).
QUESTION
Kuiper
Answer: A Deployment tool used to deploy many EPIC products.
QUESTION
Client Packs
Answer: A collection of all relevant special updates into a single patch. A cumulative collection of all new and previously installed SU's.
QUESTION
Features of a Client Pack
Answer:
- Are Microsoft Patches, *.MSPs
- Are superseding; only one patch appears to the OS
- Contain Old SUs and New SUs and are therefore cumulative
- Are specific to your organization
- Must be installed using InstallMSP.exe; no double-click
- Have a sequencing number that is always higher than any previous - Client Pack, though the numbers might not be sequential.
QUESTION
InstallMSP.exe
A representative client is a machine with Hyperspace on the same code version as all other machines that support the Epic operational database environment currently being updated. By validating against a representative client, you are validating against the current state of your Epic infrastructure instead of what you believe the current state to be.
QUESTION
When you click Validate in the InstallMSP.exe GUI, what is actually being validated?
Answer: InstallMSP validates that the Client Pack is cumulative; InstallMSP can refer to the Hyperspace client while performing this validation; it's not actually checking to ensure the client is in a particular state, but rather it is checking that all SUs that are already installed on your representative client are included in the new Client Pack. For this reason, a clean machine is a particularly poor choice; because a clean machine has no installed SUs, and because zero SUs is always a subset of any Client Pack, validation will always succeed against a clean machine.
QUESTION
What error message will you receive if the InstallMSP fails due to missing SU's?
Answer: "The Client pack is missing an SU that was already included in a previous client pack. Please provide and override list.
QUESTION
What action should be completed before you run your InstallMSP batch file to update your Hyperspace clients?
Answer: You should wait for the Operational Database Administrator, ODBA, to update the relevant Epic operational database environment.
QUESTION
Rolling Updates
Answer: For organizations that use a published application to present Hyperspace, such as Citrix XenApp and/or VMWare View RDSH, you will update your servers in waves as opposed to all at once.
QUESTION
How does information about which SUs are on which Hyperspace clients get to System Pulse?
Answer: When a Hyperspace client successfully connects to an Epic environment, the client sends information about the installed SUs to the environment. The environment in turn then sends that information to System Pulse.
QUESTION
Admin.log
Answer: The Admin.log can be used to review any actions performed upon the Hyperspace Administrative Image, including its creation. These logs are stored in C:\ProgramData\Epic\v8.5\Install Data.
QUESTION
Install.log
Answer: The Install.log can be used to review any actions performed upon the Hyperspace client, including the initial installation. However, Install.log doesn't actually list the SUs that have been applied; it only lists the Client Packs that have been applied. These logs are stored in C:\ProgramData\Epic\v8.5\Install Data.
QUESTION
For a Hyperspace client that has been maintained following standard workflows and best practices, how many entries will the Install.log contain?
Answer:
- The ECSA pre-deploys the new Hyperspace client well in advance of the upgrade.
- On the night of the upgrade, the ODBA upgrades the Epic environment.
- On the night of the upgrade, the ECSA switches full client shortcuts and published applications to the new release.
- Later, the ECSA removes the old release of Hyperspace at their convenience.
QUESTION
Why should the Epic operational database environment be updated before a Client Pack is applied to your Hyperspace clients?
Answer: The new Hyperspace Client Pack likely introduces new dependencies on the Epic operational database environment. It is very common for updates to have both client and server components. It is okay for the server to have these updates before the client, in which case it may appear to the end user through Hyperspace that neither the client nor server changes are in place. Server code never introduces dependencies on the client, but the client frequently introduces dependencies on the server.
QUESTION
What is the purpose of the InstallMSP UI
Answer: The InstallMSP.exe validates that the Client Pack delivered by Epic is cumulative and contains all Special Updates already installed on a representative client. This is also where you would specify SUs that were intentionally removed.
QUESTION
Why is it important to create the InstallMSP batch file ahead of update night? Answer: If InstallMSP's validation step uncovers an issue with your Client Pack, you will have time to work with Epic to correct the problem or to receive a new Client Pack.
QUESTION
When will users use SRO, and for what purpose?
Answer: The PRD environment is unavailable, users connect to RPT environment using SRO to have read-only access.
QUESTION
What considerations should you make as you prepare for a Hyperspace Upgrade? Choose all that apply
Answer: a. [Correct] Separate out other major infrastructure changes, like upgrading hardware. b. [Correct] Review Epic's Target Platform documentation to ensure your platform is on target. c. [Incorrect] Validate your new release's Hyperspace msi well before your planned upgrade night. d. [Incorrect] Make sure the environment is upgraded before you install the new Hyperspace release.
QUESTION
You should validate Client Packs against a "representative client." Which of the following describes a representative client? Choose one.
Answer: a. [Incorrect] A clean machine with no previous Client Packs installed b. [Incorrect] A machine with only the previous Client Pack installed c. [Correct] A machine with the same Client Pack as most others machines for a given environment d. [Incorrect] A machine that already has the new Client Pack installed
QUESTION
