Na2009 enus sp_05

Chapter 5: Integration

5-1

CHAPTER 5: INTEGRATION Objectives

The objectives are:

• Demonstrate how Microsoft Dynamics NAV supports web services. • How to leverage Web Services by using Employee Portal

Introduction Microsoft Dynamics® NAV 2009 allows business logic to be published as web services, which makes integrating Microsoft Dynamics NAV with other systems much easier than previously.

This chapter will define Web Services and discuss ways that Microsoft® Office SharePoint® Server 2007 is able to consume them from Microsoft Dynamics NAV 2009, through both Employee Portal and directly from exposed web services.

Because of time constraints, this chapter will focus on the extensive out-of-the box functionality provided by Employee Portal, which is shown in the Cronus Global Website collection discussed in chapter 1 of this course.

NOTE: To learn more about working with Web Services directly using Microsoft Visual Studio, Microsoft Office InfoPath, and so on, refer to http://blogs.msdn.com/b/pchriste/ or http://blogs.msdn.com/b/freddyk/For excellent, in-depth, and current treatment of web services.

You will work on labs that will demonstrate how to:

• Extend the Cronos Global Web Site so that users can interact with the Jobs module in Microsoft Dynamics NAV 2009.

• Set up new Web Services in Microsoft Dynamics NAV 2009 using Employee Portal. Then show how to consume them in Microsoft Office SharePoint Server 2007 using a new subsite you will create and set up in the Cronus Global Web site collection.

Microsoft Official Training Materials for Microsoft Dynamics®

Your use of this content is subject to your current services agreement

Microsoft SharePoint Technologies and Microsoft Dynamics® NAV 2009

5-2

Web Services Overview The World Wide Web Consortium (W3C), which is regarded by the industry as the keeper of web standards (including XML and Web Services), describes Web Services as follows

"Web Services provide a standard means of interoperating between different software applications, running on a variety of platforms and/or frameworks. Web Services are characterized by their great interoperability and extensibility, as well as their machine-processable descriptions thanks to the use of XML. They can be combined in a loosely coupled way in order to achieve complex operations. Programs providing simple services can interact with each other in order to deliver sophisticated added-value services."

MSDN Online has the following description of XML Web Services:

"XML Web Services are the fundamental building blocks in the move to distributed computing on the Internet. Open standards and the focus on communication and collaboration among people and applications have created an environment where XML Web Services are becoming the platform for application integration. Applications are constructed using multiple XML Web Services from various sources that work together regardless of where they reside or how they were implemented."

Web Services are a standardized way for independent software systems to communicate with one another over standard Internet protocols. XML is used to define the interface as well as the data that is exchanged by the interface. Web Services architecture is designed to allow programs to communicate with each other that may be written n different languages, even on different platforms, in a language-independent, platform-independent manner.

Different software manufacturers may have different implementations of web services, and there may be minor differences in the way that their interfaces are developed. A few things, however, are common to most of these definitions:

• Functionality is exposed through a standard web protocol, such as HTTP or SOAP.

• The interface is described by using a common Web Services Description Language (WSDL), which uses XML.

• Public Web Services are registered with Universal Discovery Description and Integration (UUDI).

Web Services use XML to describe machine-readable metadata. This metadata is used to describe the message interchange formats that a Web service supports, the valid message exchange patterns of the Web service itself, as well as the capabilities and requirements of a service.




5-3

Web Services Description Language (WSDL), an XML-based language for defining Web Services, is used to express the interchange formats and message exchange patterns of the Web Services. Many major software development environments, such as Microsoft Visual Studio, can be used to build applications that use Web Services. Because Web Services are XML based, Web Services can be built across platforms and programming languages.

Web Services Architecture

With Microsoft Dynamics NAV 2009 it is possible to publish codeunits and pages as Web Services. They provide access to internal business logic in a standard format, using standard protocols. External systems can read and write data on pages and call codeunits as defined by the common Web Service protocols, with correct authentication and authorization.

Web Services published with Microsoft Dynamics NAV 2009 can provide the same functionality to an external application used within the application. The credentials of the application used to consume a Web service in Microsoft Dynamics NAV 2009 must be set up with the proper permissions to access the information.

Microsoft Dynamics NAV Web Services are useful to customers and partners who want to use Microsoft Dynamics NAV business logic or use a standard interface to access data from outside Microsoft Dynamics NAV.

Microsoft Dynamics NAV Web Services

Microsoft Dynamics NAV can publish several simple types of web services.

• The simplest web service type uses the page object. By publishing a page object, Microsoft Dynamics NAV constructs a web service that has a set of default database methods, such as Create, Read, Update and Delete operations. Publishing pages as web services provides indirect access to the Validation triggers in the underlying tables.

• Another web service type uses codeunits and the functions defined within those codeunits. Publishing a codeunit provides the functions in the codeunit as methods of the web service.

• The last type of web service includes the ability to pass complex data types by using an XML port object as a parameter in a codeunit function.

Pages and/or codeunits can be published as a web service by inserting a reference to the page or codeunit into the web service table, and marking it as a published web service. They are immediately published and available for web service requests over the network.

The Microsoft Dynamics NAV Business Web Services server application is implemented as a Windows Service that can be installed on the server. The complexity in manually setting up the frame work and managing the WSDL description is handled by this service.




5-4

Consumers of these web services, which are systems integrating with Microsoft Dynamics NAV, only have to know the network name (or address) of the computer that is running Microsoft Dynamics NAV Server and the names given to the individual pages and codeunits.

For example, with the following configuration:

• Computer name that runs Microsoft Dynamics NAV Service: NAV_SRV_01

• Web Service port: 7047 • Microsoft Dynamics NAV instance: DynamicsNAV • Company Name: CRONUS International Ltd. • The published page Web service: MyCustomer

Then the MyCustomer Web Service is available at the following URL:

http://NAV_SRV_01:7047/DynamicsNAV/WS/CRONUS_International_Ltd/Page/MyCustomer (http://nav_srv_01:7047/DynamicsNAV/WS/CRONUS_International_Ltd/Page/MyCustomer)

Microsoft Dynamics NAV manages Web Service requests exactly the same as it handles requests from end-users within the Classic Client or the Role Tailored Client. User rights authorization and validation, input data validation, business logic invocation, and concurrency control are all managed in the same manner as requests from a Microsoft Dynamics NAV client.

This guarantees that the integrity of the Microsoft Dynamics NAV data is not compromised by using Web services. It also means code which validates data, or invokes business logic for systems using the Web Services provided by Microsoft Dynamics NAV, does not have to be replicated.

Historical Integration Options

Historically, Microsoft Dynamics NAV offers some integration possibilities by using the following technologies:

• C/Front • C/ODBC • OCX • Automation • NAV Application Server (NAS

These integration options have their own advantages and disadvantages, and choosing the best technology is case dependent.

With the release of Microsoft Dynamics NAV 2009, Web Services have been added to provide a new method of integrating with the system. Because Web




5-5

Services use industry standard protocols and technologies, the possibilities are endless. Web Services is intended to be the new basis for cooperative efforts with other technologies.

Suitable Candidates for Web Services

Web Services are suited for communication across platforms and programming languages. Microsoft Dynamics NAV 2009 makes is easy to integrate with other systems and benefit from the flexibility that Web Services offers. The following are candidates for Web Services:

• Solutions executing business logic or read data from Microsoft Dynamics NAV.

• Solutions writing data to Microsoft Dynamics NAV and using the system to validate the data with the existing business logic.

• Solutions extending Microsoft Dynamics NAV with additional information (such as: customer information, exchange rates, or product information), and having that extension be accessed from other systems.

Using Employee Portal - Creating, Exposing and Consuming Web Services

Employee Portal in Microsoft Dynamics NAV provides a web-based interface that gives users quick access to mission-critical business information such as invoices, customer data, and reports. Each time the database is modified, Employee Portal updates the system in real time, so people across the network always have access to the most current information.

Employee Portal is ideal for employees who need occasional access to Microsoft Dynamics, but do not need full user status. For example, salespeople can enter orders and view customer accounts and histories; purchasers can check on stock availability; and production designers can look up bills of material.

Employee Portal integrates with standard Microsoft collaboration and productivity tools and works with Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 to help employees work effectively.

Employee Portal is intuitive and requires a minimum of programming. It comes with out-of-the-box Microsoft .NET–based Web Parts.

Because a fully functional Employee Portal is already set up, it is not necessary to discuss every step required to create a new site. To read more about Employee Portal functionality and implementation, refer to the Employee Portal online Help.




5-6

Lab 5.1 - NAV-Creating Captions Scenario

In Employee Portal, you must define captions for text needed on your Web Parts for navigational or informational purposes that are not stored as application data. It is important to define at least one caption for each of the elements listed, and it is also important to attach captions to all instances of the elements you create. Otherwise the web client will receive an error. Because most of these are already set up, you will only add captions specific to Jobs and then use them later.

Define the following captions:

• Group Captions • Web Part Request Captions

Use the following captions as-is:

• Web Part Table Tab Captions • Part Table Action Captions • Web Setup Captions

Group Captions

In the Microsoft Dynamics NAV Classic Client:

1. Click Administration > Employee Portal. > Captions > Group Captions The EP Group Captions screen opens.

2. Click the Caption > Create New button to add a new caption. The EP Language list opens.

3. Click OK. The EP Group Captions form re-opens on a new line. 4. Click View > C/AL Globals. The C/AL Global window opens. 5. Type Jobs into the Caption field. The language should be 1033 and

the ID should be 2.

Web Part Request Captions


1. Click Administration > Employee Portal. > Captions > Group Captions The EP Group Captions screen opens.

2. Click the Caption > Create New button to add a new caption. The EP Language list opens.

3. Click OK. The EP Group Captions form re-opens on a new line. 4. Click View > C/AL Globals. The C/AL Global window opens. 5. Type Job Card into the Caption field. 6. Repeat steps 1-5 adding Job List into the Caption field.




5-7

Lab 5.2 - NAV-Setting Up Groups Scenario

A group is a collection of Web Part Requests. Web Part Requests are based on Microsoft Dynamics NAV informational and, or functionality that helps the user perform a task. Web Part Requests can be combined in a group to meet your needs. You can choose to set up a few general groups, each containing all the permissions for one user type or set up a group for each task or part of a task that users will perform. Then you can customize each user's rights and possibilities.

After a group is created, you can assign users to the group so they have access to the Web Part Requests that are assigned to that user group

Add the Jobs Group


1. Click Administration > Employee Portal. > Group The EP Group Card screen opens.

2. Click the F3 key to add a new group with the following data: a. Code: Jobs. b. Description: Jobs c. Language ID: 1033 d. Caption: Choose Jobs from the drop down menu.

Add Users to the Group

1. From the EP Group Card, navigate to the Sales group, then click EP Group > Users The EP Users Per Group Card screen opens.

2. Highlight all the users, then copy all the lines and close the form. 3. Navigate to the Sales group, then click EP Group > Users. The EP

Users Per Group Card screen opens. 4. Paste all the records you just copied into the form.




5-8

Lab 5.3 - NAV-Setting Up Web Part Requests Scenario

Define the Employee Portal Web Parts you want to make available to your users by creating a Web Part Request in Microsoft Dynamics NAV. A Web Part Request defines the format of the Web Part, the data it will present, the basic properties of the data and the control elements that will be used for interaction and to navigate between Web Parts. Meaning, it defines the data the Web Part will request from Microsoft Dynamics NAV and how it will be presented in the Web Part.

Each Web Part Request is based on a Web Part Request template. This means that you can create different Web Part Requests for different user groups but based on the same Web template. These Web Part Requests will comprise your Employee Portal. You can define Web Part Requests for different purposes. Choose from the following three types:

• List (to show a list of items) • Card (to show a record in a card) • Header + Line (to show a header with attached lines)

In the Web Part Request table, you will find a fourth type of Web Part requests called System. The System Web Part Request is defined by the program used for certain actions. More information about this type of Web Part Request is available in Creating an Action.

Web Part Request Templates

A template in Employee Portal is similar to a template in a word processing application. It is a document that contains formatting and, sometimes, generic text or other content. However, actions for interaction and navigation remain to be filled in on the individual Web Part Request. One Web Part Request template can be used as a model for creating many Web Part Requests.

When designing a template, decide what properties (attributes or characteristics) you want the parts based on that template to have. Decide the layout of each Web Part and what types of information will be included. Then you can create many Web Parts based on the same template, but that contain different information.

For example, if creating a Web Part of the type List, you can use the same basic template for many list Web Part Requests. You can then add characteristics to the Web Part Request to change the list Web Part request to suit your needs. This can be done by adding or removing fields and tabs and by defining actions and lookups.




5-9

In the Microsoft Dynamics NAV Classic Client, to add a new group with the Code: JOBCARD:

1. Click Administration > Employee Portal. > Web Part Request Templates The EP WP Request Template Card opens.

2. Click the F3 key to add a new group with the following data: a. Code: JOBCARD b. Description: Job Card c. Language ID: 1033 d. Caption: Choose Job Card from the drop down menu. e. Accept the default for other fields

3. Add a line in the lines section with the following values:

a. Table No.: 167 b. Header or Line: Header c. Accept the default for other fields.

In the Microsoft Dynamics NAV Classic Client, to add a new group with the Code: JOBLIST:

1. Click Administration > Employee Portal. > Web Part Request Templates The EP WP Request Template Card opens.

2. Click the F3 key to add a new group with the following data: a. Code: JOBLIST b. Description: Job Card c. Language ID: 1033 d. Caption: Choose Job Card from the drop down. e. Accept the default for other fields

3. Add a line in the lines section with the following values:

a. Table No.: 167 b. Header or Line: Line c. Accept the default for other fields.

Individual Web Part Request

Once you set up Web Part Request templates for your portal, create the individual Web Part Request that will comprise your Web Part. A Web Part Request must be assigned to a user group to be made available to the users assigned to the group.




5-10

Once you select the template to build your new Web Part request on, the properties from the Web Part Request template will be copied to the new Web Part Request. Some of the properties will have a default value from the Web Part Request template, but you can change the value. Define control elements in the Web Part Request such as actions buttons and links to allow interaction and navigation in the Web Parts. Once you fill in values for the properties and the controls, the Web Part Request is complete and it will be available on your portal page.


1. Click Administration > Employee Portal > Group. The EP Group Card screen opens.

2. In the lines, press F3 to add a new Web Part Request. 3. In the Code field, select the code of the Web Part request template to

base your Web Part Request on. In this case, choose JOBCARD then click Web Part Request, Card. The EP WP Request Card window appears.

4. Fill in all the fields in the header of the Web Part Request. The Web Part Request has inherited most information including the tables from the Web Part Request template you have based it on.

5. Navigate to the JOBS group.

Repeat steps 1 – 5 to add a Web Part Request for JOBLIST.




5-11

Lab 5.4 - NAV-Defining Tabs Scenario

A tab control is used to define multiple pages for the same Web Part Request to group related fields.

NOTE: For each Web Part Request, at least one tab must be set up. Otherwise Microsoft Dynamics NAV stops the processing with an appropriate message in the event log after receiving a request from the portal page.

Once a tab is defined, fields can be added to the tab and lookups can be defined to list Web Parts from the fields on the tab.

Defining Tabs

The tabs shown in SharePoint appear similar to the ones in Microsoft Dynamics NAV. In the Classic Client, click Jobs > Jobs, the Jobs card appears. Study the tabs and the fields they contain. All fields present in Microsoft Dynamics NAV will not be used in this lab.


2. Navigate to the Jobs group, then select JOBCARD in the lines. 3. Click Web Part Request > Card, the EP Request Card appears. 4. Click Table > Card, the EP WP Table Card appears. 5. In the lines section add a new line with the following data:

a. Code: GENERAL b. Description: General c. Positon: 0 d. Accept the default for other fields

6. Click Tab > Card, the EP WP Table Tab card appears 7. In the lines section add a new line with the following data:

a. Field No.: 1 (No.) b. Required: True c. Accept the default for other fields d. Repeat the steps to add fields 3 (Description) and 5 (Bill-to

Customer No.)

8. Repeat steps 1-7 to add tabs for Posting and Duration. Add some of the fields shown in the Job Card and be sure to increment the Position field so that the tabs are shown in the correct order.




5-12

9. Repeat steps 1-8 to add a General tab to the JOBLIST Web Part Request. Add the following fields in step 7. a. No. b. Description c. Bill-to Customer No. d. Bill-to Name e. Person Responsible

Tab Captions:


2. Navigate to the Jobs group, then select JOBCARD in the lines. 3. Click Web Part Request > Card, the EP Request Card appears. 4. Click Table > Card, the EP WP Table Card appears. 5. Click the Assist Edit button in the Caption field, the EP Table Tab

Captions form appears. a. If the caption needed is already available, select that line and

choose OK. b. If not, click Caption > Create New, select ENU (the default),

then OK, then type the caption, Posting for example, and then OK.




5-13

Lab 5.5 - NAV-Creating Actions Scenario

Actions in Employee Portal are used to issue commands from your Web Parts.

For example, to define an action to create a new line in a header + line Web Part, or you can define an action from a list Web Part to open the record in a card Web Part.

By using actions in your Web Parts, your users can interact with the data and navigate between Web Parts.

Creating Actions

The tabs shown in SharePoint appear similar to the ones in Microsoft Dynamics NAV. In the Classic Client, click Jobs > Jobs, the Jobs card appears. Study the tabs and the fields they contain. All fields present in Microsoft Dynamics NAV will not be used in this lab.

Click Administration > Employee Portal. > Group The EP Group Card screen opens.

1. Navigate to the Jobs group, then select JOBCARD in the lines. 2. Click Web Part Request > Card, the EP Request Card appears. 3. Click Table > Card, the EP WP Table Card appears. 4. Click Table, Actions. The EP WP Table Action List window is

opened. Click F3 to create a new line. 5. In the Type field select the relevant action. In the Target field select

Current. Fill in the remaining fields. Add new lines for the following types: a. Insert Head ,Save Record ,Delete Record b. Code: INSERTHEAD, MODIFYHEAD, DELETHEAD c. Description: Create New, Save, Delete d. Target Table No.: 167 e. Accept the defaults for the other fields

6. Repeat steps 1-6 to add an Action to the JOBLIST Web Part Request

with the following data a. Type: Connect to another WP Request b. Code: Job Card c. Target Table No.: 167 d. Accept the defaults for the other fields




5-14

Lab 5.6 - SharePoint-Create a Jobs Sub-site Scenario

Now, all the set up required in Employee Portal is complete. It is time to move to Microsoft Office SharePoint Server 2007.

This lab will demonstrate how to create a new subsite under the Cronus Global Web Site collection to be able to view and modify the Jobs data exposed in the preceding labs.

Create a New Site 1. From the Cronus Global Website main page, use the Site Actions

drop-down menu, and choose the Create menu option. 2. Click the Sites navigation tab. 3. From the Web Pages menu, select Sites and Workspaces. 4. On the New SharePoint Site page, enter the following information:

a. For Title, enter Job Department. b. For Description, enter Job Department. c. In the URL Name box, enter job. d. For Template Selection, select Document Workspace from the

Collaboration group of templates. e. Leave the other settings as they are.

5. Click the Create button and wait for the site to be created.




5-15

Lab 5.7 - SharePoint-Add Features to the Jobs Sub-site Scenario

This lab will demonstrate how to improve the new Jobs subsite created in Lab 5.7. The lab focuses on making the look and feel of the new site consistent with the rest of the collection.

Change the Theme

1. Use the Site Actions drop-down menu, and choose the Site Settings menu option.

2. From the Look and Feel menu, select Site Theme. 3. Choose a Site Theme you like, such as Verdant, then choose Apply.

Change the Title

1. Use the Site Actions drop-down menu, and choose the Site Settings menu option.

2. From the Look and Feel menu, select Title, description, and icon. 3. In the URL field type -

http://sharepoint/Contoso%20Pictures/_w/Contoso-Banner_icon_jpg.jpg, then test it.

4. Choose OK.




5-16

Lab 5.8 - SharePoint-Add Web Parts Scenario

This lab will demonstrate how to connect the new Job Department Subsite to Microsoft Dynamics NAV 2009. It uses the Employee Portal Web Parts with the setting created in the earlier labs.

Add Web Parts-Job List

1. On the home page of the Jobs Sub-site, click Site Actions and select Edit Page.

2. Delete all the Web Parts currently on the page by clicking X next to the edit dropdown menu for each one.

3. In the Left Web Part Zone, click the Add a Web Part button. 4. In the Add Web Parts form, under Miscellaneous select List Web

Part for Navision Employee Portal, and then click the Add button. 5. The Ep List Web Part now displays in the left Web Part zone of

your home page. 6. In the Ep List Web Part, select edit, Modify Shared Web Part, the

EP List Web Part Properties sheet now appears on the right of the screen.

7. Under Group, choose Job. 8. Under Web Part Request, choose Job List. 9. Choose OK, the Web Part should now show a list of the Jobs

currently in NAV.

Job Card


2. In the Left Web Part Zone, click the Add a Web Part button. 3. In the Add Web Parts form, under Miscellaneous select Card Web

Part for Navision Employee Portal, and then click the Add button. 4. The Ep Card Web Part now displays in the left Web Part zone of

your home page. 5. In the Ep Card Web Part, select edit, Modify Shared Web Part,

the EP Card Web Part Properties sheet now appears on the right of the screen.

6. Under Group, choose Job. 7. Under Web Part Request, choose Job Card. 8. Choose OK, the Web Part should now show a list of the Jobs

currently in NAV.




5-17

Job Card

1. On the home page of the Jobs Sub-site, click Site Actions and select Edit Page. In the Left Web Part Zone, click the Add a Web Part button.

2. In the Add Web Parts form, under Miscellaneous select Card Web Part for Navision Employee Portal, and then click the Add button.

3. The Ep Card Web Part now displays in the left Web Part zone of your home page.

4. In the Ep Card Web Part, select edit, Modify Shared Web Part, the EP Card Web Part Properties sheet now appears on the right of the screen.

5. Under Group, choose Job. Under Web Part Request, choose Job Card.

6. Choose OK, the Web Part should now show a list of the Jobs currently in NAV.




5-18

Lab 5.9 - SharePoint-Connecting Web Parts Scenario

When you have created a list or a header + line Web Part, it can be useful to present the details of a record in the lines, in a card Web part. You can do that by using action to connect the two Web Parts. This way you can for example make a connection from a list of customers to a customer card that will give you the details about the selected customer.

Connect the Card and List Web Parts


2. In the Job List Web Part, select edit, Modify Shared Web Part, Connections, Send EP Parameter to, Job Card

3. Choose Exit Edit Mode just under the Site Actions menu. 4. Now from the Job List, select Card from one of the Job Lines, the

Job Card will now display the record for the Job chosen..




5-19

Summary In this chapter you learned to integrate Microsoft Dynamics NAV 2009 with Microsoft Office SharePoint Server 2007 using Employee Portal in Microsoft Dynamics NAV 2009.

Some of the topics covered include:

• Web Services • In Microsoft Dynamics NAV 2009

o Employee Portal o Creating Captions o Setting up Groups o Setting up Web Part requests o Defining Tabs o Creating Actions

• In Microsoft Office SharePoint Server 2007

o Create a new sub-site o Add features to a sub-site o Add Web Parts to a page o Connect Web Parts to each other




5-20

Test Your Knowledge 1. What are Web Services?

2. What is the common language called that describes Web Services?

3. Which two object types in Microsoft Dynamics NAV can be published as Web Services?




5-21

4. How are Microsoft Dynamics NAV objects published as a Web Service?

5. Which general database operations are provided by page Web Services?

6. Name two technologies that can be used to consume Web Services?




5-22

Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter

1.

2.

3.




5-23

Solutions Test Your Knowledge

1. What are Web Services?

MODEL ANSWER:

Web Services are a standardized way for independent software systems to communicate with each other over standard Internet protocols.

2. What is the common language called that describes Web Services?

MODEL ANSWER:

Web Services Description Language, or WSDL

3. Which two object types in Microsoft Dynamics NAV can be published as Web Services?

MODEL ANSWER:

Pages and Codeunits

4. How are Microsoft Dynamics NAV objects published as a Web Service?

MODEL ANSWER:

By entering a reference to them in the Web Services form, and putting a checkmark into the Published field.

5. Which general database operations are provided by page Web Services?

MODEL ANSWER:

Create, Read, Update and Delete.

6. Name two technologies that can be used to consume Web Services?

MODEL ANSWER:

Microsoft Visual Studio and Microsoft Office Infopath.




5-24



Date post:	07-Nov-2014
Category:	Technology
Upload:	peter-muscat
View:	467 times
Download:	2 times

Na2009 enus sp_05

Technology