Book contents
- Frontmatter
- Contents
- Preface
- List of abbreviations
- Part I Preparation for OPNET Modeling
- Part II Modeling Custom Networks and Protocols
- Part III Modeling and Modifying Standard Networks and Protocols
- Part IV OPNET Modeling Facilities
- 11 Debugging simulation
- 12 OPNET programming in C++
- 13 Traffic in OPNET simulation
- 14 External model access (EMA)
- 15 OPNET co-simulation with third-party programs
- 16 Model authoring and security
- References
- Index
16 - Model authoring and security
from Part IV - OPNET Modeling Facilities
Published online by Cambridge University Press: 05 February 2012
- Frontmatter
- Contents
- Preface
- List of abbreviations
- Part I Preparation for OPNET Modeling
- Part II Modeling Custom Networks and Protocols
- Part III Modeling and Modifying Standard Networks and Protocols
- Part IV OPNET Modeling Facilities
- 11 Debugging simulation
- 12 OPNET programming in C++
- 13 Traffic in OPNET simulation
- 14 External model access (EMA)
- 15 OPNET co-simulation with third-party programs
- 16 Model authoring and security
- References
- Index
Summary
OPNET Modeler provides an authoring tool to allow authors to protect their models against unauthorized use. This chapter demonstrates how to use this authoring tool to protect and license user OPNET models. In order to follow this chapter, a reader should understand the basic concepts of OPNET models.
Introduction
In practice, you often need to publish models to allow other people to use them. However, sometimes you want them only to use these models but not to view the implementation details of these models, and/or to use these models for a limited time, like a demo version with limited access ability. To handle these issues, OPNET Modeler provides an authoring tool that allows you to encrypt your models to provide three levels of access: Use, Inspect, and Full. For “Use” access, users can only use the model in a simulation, but cannot inspect this model's structure or code via either the GUI editor or programming interface. For “Inspect” access, users can use this model in a simulation and inspect the model with certain programming interface procedures, but cannot view the structure of the model via the GUI editor. For “Full” access, users have full access to the model, i.e. they can use it, view it, and modify it in either the GUI editor or programming interface. By default, a model is not protected by the authoring tool, which therefore has “Full” access.
- Type
- Chapter
- Information
- Unlocking the Power of OPNET Modeler , pp. 232 - 235Publisher: Cambridge University PressPrint publication year: 2012