Get-ASAppServiceEndpoint

Get-ASAppServiceEndpoint

Gets information about endpoints exposed by the specified service.

Syntax

Parameter Set: SiteNameAndVirtualPath
Get-ASAppServiceEndpoint [-SiteName] <String> [-VirtualPath] <String> [ <CommonParameters>]


Detailed Description

This cmdlet returns system endpoints, default application endpoints, and application endpoints defined in a Web.config file. A system endpoint is an endpoint that the AppFabric system adds to the service automatically. A default application endpoint is the endpoint that is added to the application based on the protocols supported on the application. An application endpoint is the endpoint you define in a Web.config file. Any other endpoints that are created dynamically created at runtime using the code are not returned.

System endpoint types are defined in the endpointExtensions section in the machine.config (for example, discoveryEndpoint). However there is an exception to this rule for workflowControlEndpoint and serviceMetadataEndpoint. The first endpoint is added to the service when you enable instance control by using Set-ASInstanceManagement cmdlet or by using Workflow Host Management tab of the Configure Service dialog box and the second endpoint is added when enable metadata access over HTTP by using the Configure Service dialog box.

.NET Framework 4.0 adds an application default endpoint for all tag-less services in a Web application for each protocol enabled on the application. For example, if the http protocol is enabled for an application, an endpoint with basicHttpBinding is added to the service and if the net.pipe protocol is enabled for an application, an endpoint with netNamedPipeBinding is added to the service. The binding to protocol mapping can also be configured in the protocolMapping section in Machine.config. To view protocols enabled for an application, right-click the name of the application in IIS Manager tree view, point to Manage Application, and then click Advanced Settings.

This cmdlet does not allow you to configure system endpoints and default application endpoints, but it does allow you to configure application endpoints specified in a Web.config file.

The Endpoint Type in the output of this cmdlet displays System for system endpoint points, Default for application default endpoints and Configured for application endpoints configured in a configuration file.

Parameters

-ServiceObject<ServiceInfo>

The name of the ServiceObject, which specifies that the cmdlet will operate on that service. This parameter is typically used to pipe the output of the Get-ASAppService cmdlet to a cmdlet containing the ServiceObject parameter.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByValue)

Accept Wildcard Characters?

-SiteName<String>

The name of a Web site, as defined in the IIS Connections pane, which specifies that the cmdlet will operate at the scope of that site, or at the scope of an application, virtual directory, or service contained within that site. To the SiteName parameter, you can add the VirtualPath parameter that identifies an application, directory, or service included in the site.

For an application or virtual directory, the virtual path includes the name of the application, as defined in IIS. For a service, the virtual path includes the name of the application, a forward slash, and the name of the .svc file or .xamlx file for the service. The VirtualPath parameter is not necessary for the site scope. The leading "/" character in the virtual path is optional. If you use the SiteName parameter, do not use the Uri parameter.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

-Uri<Uri>

A URI for an IIS site, application, virtual directory, or service, which specifies that the cmdlet will operate at that scope. If you use the Uri parameter, do not use the SiteName parameter or the SiteName and VirtualPath parameter set.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

-VirtualPath<String>

The virtual path for an application, directory, or service, as defined in the IIS Manager Connections pane, which specifies that the cmdlet will operate at the application, virtual directory, or service. You must add the VirtualPath parameter to the SiteName parameter, using SiteName to identify the site that the application, directory, or service is contained within. The leading "/" character in the virtual path is optional.

For an application, the virtual path includes the name of the application, as defined in IIS. For a service, the virtual path includes the name of the application, a forward slash, and the name of the .svc file or .xamlx file for the service. If you use the SiteName and VirtualName parameter set, do not use the Uri parameter.


Aliases

none

Required?

true

Position?

2

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • ServiceInfo


Outputs

The output type is the type of the objects that the cmdlet emits.

  • None.


Examples

Example 1

This command gets the endpoints for a service named MyWFService.


get-asappserviceendpoint -sitename "Default Web Site" -virtualpath /MyWFService/Service1.xamlx////sample outputName :Address :Binding : basicHttpBindingContract : *Kind :BindingConfiguration :EndpointConfiguration :SiteName : Default Web SiteServiceVirtualPath : /MyWFService/Service1.xamlxIsLocal : FalseIsBindingConfigurationLocal :EndpointType : Default////Name :Address :Binding : serviceMetadataHttpGetBindingContract : serviceMetadataHttpGetContractKind :BindingConfiguration :EndpointConfiguration :SiteName : Default Web SiteServiceVirtualPath : /MyWFService/Service1.xamlxIsLocal : TrueIsBindingConfigurationLocal :EndpointType : System////Name :Address :Binding : netNamedPipeBindingContract : System.ServiceModel.Activities.IWorkflowInstanceManagementKind :BindingConfiguration :EndpointConfiguration :SiteName : Default Web SiteServiceVirtualPath : /MyWFService/Service1.xamlxIsLocal : FalseIsBindingConfigurationLocal :EndpointType : System
Show: