1. What is "SOA"? Web Service?
"SOA" stands for Service Oriented Architecture and expresses a perspective of software
architecture that defines the use of services to support the requirements of software developers.
In a SOA environment, resources on a
network are made available as independent services that
can be accessed without knowledge
of the un
derlying platform implementation. SOA is both an
architecture and a set of best practices and patterns. Web Services are XML representations of
ects, messages, or documents accessible by applications for the purpose
application to application interaction.
provides a set of principles or governing concepts used during phases of systems
development and integration. Such an architectur
functionality as interoperable
A Web Service
software system designed to support interoperable machine
machine interaction over a network. It has an interface described in a machine
format (specifically W
eb Services Description Language WSDL). Other systems interact with
the Web service in a manner prescribed by its description using SOAP
, typically conveyed using HTTP with an XML serialization in conjunction with other
2. Why do we care about web services?
Web Services will enable more IT activity. More people will have access to interesting data that
can be used in creative ways to develop new solutions, applications and mashups.
3. What is BYU doing to
create and support Web Services?
The Web Services effort at BYU has made great strides in 2009. A governance board ("EGAB")
with members from across campus, was formed and policies created that laid the foundation for
cooperation and collaboration for web
application development. The SOA Registry was
deployed that provides a common registry for available web services.
4. What is “EGAB”?
The Enterprise Governance Advisory Board for Web Services was formed in early 2009 with
representation of several key de
partments and colleges across campus.
5. Where is the link for the SOA Registry?
There is a production instance (
) as well as a test instance
). The latter site is used to test and validate web
services for policy compliance and functionality before it is made available to consumers.
Can I log into the SOA Registry?
Yes. Your current NETID and password are used for authentication and access into the registry.
7. Can I view all current Web Services available?
Yes. By default, you should be able to view all web services currently availa
ble. The ability to
consume, or use the web service is dependent on your current status and role with the University.
8. Can I view upcoming and future Web Services in development?
Yes. The list of requested web services are found on the EGAB Wiki at:
9. Who is my Organizational Administrator for Web Services?
This can be viewed by logging in to the test
registry and selecting the organization most closely
related to your department, or college. The "Organization Overview" section contains the contact
name and information for your Organizational Administrator.
10. Does it matter what development environmen
t I use to develop Web Services?
11. Are there costs, charges associated with using Web Services?
. Do all web services run in the Data Center?
No. Web services can be run anywhere that the developer of the web service chooses.
. Does my appli
cation have to reside in the Data Center?
. What if the provider of a Web Service disables, or removes a Web Service I am using?
Every effort has be
taken to ensure that this event does not occur. In the event that it does, the
Help Desk (x24000) should be able to help. Consumers of web services are notified by the
provider when changes are planned.
. How do I know who created a specific service tha
t I want to use?
Support information can be found as a document attachment under the "Metadata"
tab of the
specific web service in the registry
. Who do I call for support for specific Web Services?
Call x24000 and you will directed to the provider of t
he Web Service.
. Where can I find information on the operations in a service and how to use them?
Select the "Operations" tab within the specific web service.
. What support does the SOA Registry provide with regard to user authentication?
The SOA Re
Basic NetID and Password Authentication or
within the platform
depending on the requirements of each web service
. How do I enable authorization to my Web Service?
Authorization is controlled within the individual appl
ication. All rights, control and access
currently afforded from a specific application, or data store is also made available via a web
The ability to provide access to operations in web services using LDAP groups is under
. How do
I submit an idea for a new Web Service?
Contact your Organizational Administrator, or send an email request to John Sutherland at
. How do I gain access to a Web Service?
Access to web services are
gained programmatically. Each web service has a WSDL associated
with it that describes how an application should interact with the web service itself. Within the
registry both the operations, WSDL, and instructions on use can be found.
. What is the dif
ference between a Physical and Virtual Web Service?
A physical web service is the actual location of the application running on a server. Virtualizing
a web service provides a layer of abstraction that enables better security, the ability to load
and mediation for message content transformation.
Virtual Web Services can be
accessed via calls to the endpoints in the SOA Registry. Physical endpoints cannot be called
23. What policies does my
ervice need to follow?
EGAB has defined pol
icies for the development and consumption of web services. These
policies can be located at the following address:
The policies are organized and grouped according to life cycle phase that EGAB has organized
and put into place to assist in web service governance.
24. Once I submit a Web Service how long does approval take? How is i
t moved into
Web Services are submitted to the test registry where they are tested for compliance and feature
functionality. Once tested and approved, the web service is submitted for approval to be placed
into production. OIT Operations has be
en tasked to promote the approved services to production.
This is a new process and the actual duration is unknown at this time. Hopefully the entire
an take place in a few days.
25. Is there a checklist I must know about before I can publish a W
You can find the four checklists that have been defined and approved at
. The certification checklist must be
completed to move
a web service from test into production.
26. Will Production Services support my Web Service for me after hours, or on weekends
Yes. Requests can be submitted directly to the Service Desk at x24000. All support information
is stored in docume
ntation attached as metadata directly with the web service.
27. Can 3rd party
BYU personnel access and consume our Web Services?
Anyone with a valid BYU NETID and password may access web services. Access to data and
other web service
operations are determined by the individual
s role with the University.
28. What, if anything, do I do in the event that my application and/or Web Service is hosted
Call the Service Desk (x24000) in order to have special setting enabled for you
29. As a publisher of Web Services, can I see who is using it? Can I notify my users in the
event of planned outages, or upgrades?
Yes. As a provider you may see which users and systems are consuming your web services and
operations associated with those applications.
30. Can Web Services be used in the creation of myBYU portlets?
Yes. There are special instructions
, and SDK
w to" documentation coming soon.
31. Are SOAP, REST and POX
ervices all supported?
all three are supported.
32. What is SOAP?
SOAP stands for Simple Object Access Protocol which is t
he standard for web services
messages. Based on XML, SOAP defines an envelope format and various rules for describing its
contents. Seen (with WSDL and UDDI)
as one of the three foundation standards of web services,
it is the preferred protocol for exchanging web services, but by no means the only one;
proponents of REST say that it adds unnecessary complexity.
33. What is REST?
REST stands for REpresentationa
l State Transfer. REST
is a style of software architecture for
distributed hypermedia systems such as the World Wide Web. The term Representational State
Transfer (REST) was introduced and defined in 2000 by Roy Fiel
34. What is POX?
"Plain Old XML",
or "POX", is basically just XML. POX is complimentary to REST where
REST refers to a communication pattern and POX implies an informational format style.
35. Where can I get training on how to create
There are many sources. On campus, howeve
r, you may contact John Sutherland who is
responsible for the SOA
of Excellence. There are many resources and trained individuals
who can assist. For training specific to the SOA Registry, or the SOA Registry Platform, the
Service Desk may also answer
some basic questions.
36. What is the SOA
A collection of SOA experts on campus who are available to assist with web services
development and application development involving web services.
40. What Service Level agreement is in place
for the platform? For each service?
SLAs are available within the SOA Registry Platform and are defined differently for each web
service. Specific information on each can be found within the SOA Registry.
41. What environment or tool set should I use to cr
eate web services?
That is up to the individual developer's preference and training. This will be different for each
developer and is dependent on his/her skills and system requirements.