OSS Mobile Solution Uptake Guide

642 views
509 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
642
On SlideShare
0
From Embeds
0
Number of Embeds
94
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

OSS Mobile Solution Uptake Guide

  1. 1. OSS MOBILE SOLUTION UPTAKE GUIDE January 2013
  2. 2. OSS MOBILE SOLUTION UPTAKE GUIDE Page 1 OSS Mobile Solution Uptake Guide, Release 7.2.2 Copyright © 2005, 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
  3. 3. OSS MOBILE SOLUTION UPTAKE GUIDE Page 2 OSS Mobile Solution Uptake Guide Introduction........................................................................................................4 Purpose................................................................................................................4 Requirements Not Addressed .....................................................................5 Glossary...............................................................................................................5 Solution Architecture and Deployment Model.............................................6 Set Up..................................................................................................................6 Packages for Download ...............................................................................7 Server Platform Components......................................................................8 Single Domain Deployment....................................................................8 Multiple Domain Deployment ...............................................................8 Server Applications.......................................................................................9 Solution Development Desktop .................................................................9 Messaging Resource Adapter ....................................................................11 Mobile Solution Installer............................................................................12 Solution Components.................................................................................14 OSM Cartridges ......................................................................................14 OSM Workgroup Membership.............................................................17 WebLogic Credentials............................................................................18 ASAP Cartridges.....................................................................................19 UIM Tech Pack Deployment................................................................20 UIM Solution Development.................................................................20 Operations and Readiness..............................................................................20 UIM Readiness ............................................................................................21 Locations..................................................................................................21 Mobile Serving Area...............................................................................21 Service Profiles........................................................................................23 SIM Cards and IMSIs.............................................................................23 ASAP Readiness..........................................................................................24 Configuring Network Elements using Design Studio’s NEP Map.24 Configuring Network Elements using SACT.....................................26 Restart ASAP...........................................................................................27 Sample EBM Orders for Mobile...................................................................27 Order Template creation............................................................................27 Template Creation – A walkthrough ...................................................28 Order Template editing..............................................................................29 Template editing – A walkthrough ......................................................29 Demonstration .................................................................................................29 Add Mobile ..................................................................................................30 Add Mobile with a Reserved Telephone Number Using OSM web UI 30 Add Mobile with a Reserved Telephone Number.............................31 Add Mobile with a Port-in Telephone Number ................................31 Cancel Scenario.......................................................................................31 Retry Scenario .........................................................................................32
  4. 4. OSS MOBILE SOLUTION UPTAKE GUIDE Page 3 Resume Scenario.....................................................................................32 Suspend Mobile...........................................................................................32 Resume Mobile............................................................................................32 Change Mobile.............................................................................................32 Change Mobile to add GPRS................................................................32 Change Mobile to remove GPRS.........................................................33 Disconnect Mobile......................................................................................33 Disconnect...............................................................................................33 Disconnect Mobile with a Port-Out Telephone Number................33 Troubleshooting...............................................................................................33 Frequently Encountered Problems...........................................................34 Not enough logging from OSM to diagnose failures........................34 JMS Store-and-Forward forwarded a message from OSM, but the message never arrives at the remote system.......................................................................................................34 OSM continually retries executing the automation plug-in due to message re-delivery. 34 UIM cartridge deployment fails to find Extension Point.................34 ASAP fails to send events. ....................................................................34 Appendix A: Contents of the Mobile Service Provisioning Solution Media Pack 34
  5. 5. OSS MOBILE SOLUTION UPTAKE GUIDE Page 4 OSS Mobile Solution Uptake Guide INTRODUCTION This solution uptake document describes the setup procedures for adopting the GSM mobile service provisioning solution. This document serves as the basis for developing demonstrations, proofs of concept, and service provisioning solutions for deployment into production environments. This mobile service provisioning solution was developed for Release 2 of the suite of Oracle Communications OSS applications for service fulfillment, which is composed of the following applications and components. • ASAP 7.2.0, an automatic service activation program • Order and Service Management (OSM) 7.2.2 • Unified Inventory Management (UIM) 7.2.2 • Design Studio 7.2.2 PURPOSE This solution implements add, suspend, resume, change, and disconnect actions for mobile service, including GSM voice, GPRS data (Internet access), SMS text messaging, and voice mail. These actions can be requested by capturing a service order and submitting it for execution (provisioning) in OSM. The service is automatically designed using a service configuration in UIM to allocate resources (e.g., telephone number, home location register, voice mail server, subscriber accounts) and configure them to support the service. Finally, this design is delivered by submitting an order to ASAP to activate the configuration in the network against the Ericsson HLR and the Comverse VVMS Insight (voice and video mail server). The provisioning process implements a fully automated success path with human intervention for failures. The mobile service provisioning solution provides a foundational implementation of an end-to-end provisioning process that includes integration with OSM, UIM, and ASAP. The key technical objectives are: • Modeling of a service order with order items that can carry actions on services. • Modeling of a OSM cartridge with composite cartridge projects • Modeling of a provisioning process that can process order items through a design sub-process followed by delivery. • Configuration of all necessary JMS modules, SAF agents, SAF contexts, SAF imported destinations, Queues, Topics, and Messaging Bridges. • Modeling of automation tasks for each system interaction in the provisioning process. • Implementing the XQuery scripts needed for each system interaction (application integration) to send each request message and to receive each response, fault, or event message. • Implementing and demonstrating the Web Service operations used to design a service configuration in UIM and manage the life cycle of the service and its configuration through the entire provisioning process. • Demonstrating the use of UIM to automate the design of a service configuration. • Demonstrating the use of the productized GSM technology pack for UIM within a solution. • Demonstrating the use of Web Service operations for ASAP to activate a service and its configuration in the network.
  6. 6. OSS MOBILE SOLUTION UPTAKE GUIDE Page 5 • Demonstrating service abstraction in ASAP to decouple the solution from the choice of devices in the network. • Demonstrating the use of the productized Ericsson HLR and Comverse VVMS Insight cartridges for ASAP within a solution. • Demonstrating the transformation of product actions from a Provisioning Order to the service actions on a Service Order. This illustrates how the OSS suite of applications implements the provisioning function as a component of the Oracle Application Integration Architecture (AIA) Order-to-Activate Process Integration Pack (PIP). The key business objectives of this solution are: • Illustrate through an actual implementation the solution architecture for implementing a provisioning solution. • Provide the foundation for Oracle consulting, sales engineers, and technical marketing to further develop into proofs of concept, demonstration, and production systems. This solution shall serve as a reference implementation. • Provide a basis for refining and evolving the solution architecture into future releases of the OSS Suite, which will deliver more complete solutions, better integration, and better architectural alignment across the portfolio. • Provide a solution to drive OSS Suite performance benchmarking. Requirements Not Addressed The solution is subject to the following simplifications: • Telephone number reservation is not supported through a Web Service for integration with CRM for Order Capture. • Scheduling delivery for a future dated action on the order is not supported. • Order revisions and amendments (with undo and redo) are not supported. • Order cancelation (with undo) is not supported. GLOSSARY ASAP – Automatic Service Activation Program AIA – Application Integration Architecture DN – Distinguished Name JMS – Java Messaging Service OSM – Order and Service Management OSS – Operations Support System SAF – JMS Store-and-Forward UIM – Unified Inventory Management
  7. 7. OSS MOBILE SOLUTION UPTAKE GUIDE Page 6 SOLUTION ARCHITECTURE AND DEPLOYMENT MODEL Figure 1 shows a single domain deployment model. Figure 1 – Single Domain Deployment Diagram Figure 2 shows a multiple domain deployment model. Figure 2 – Multiple Domain Deployment Diagram SET UP The set up procedure can be summarized as follows:
  8. 8. OSS MOBILE SOLUTION UPTAKE GUIDE Page 7 1. Confirm that the user is prepared to set up the solution. a. Hardware is available – the machines have a server operating system set up with network connectivity. The user knows the IP addresses, host names, and the account passwords for root and the application administrator. b. Installation options - the user has decided upon the Oracle Database and application server deployment configuration (e.g., Database RAC, application server clustering), and the allocation of hardware resources to support this configuration. c. Storage space and network file system set up – enable all machines to have access to a network file system that enables a single WebLogic domain to be shared by all application servers. 2. Download the packages. (approx. 2 hours) 3. Install the server platform components to reflect the desired server deployment model. (approx. 1 hour) 4. Install the server applications. (approx. 2 hours) 5. Install the solution development desktop environment. (approx. 1 hour) 6. Run the mobile solution installer. (approx. 10 minutes) 7. Install the mobile solution components. (approx. 1 hour) Each of these steps will be detailed in the subsections below. Packages for Download The following packages of platform and application components must be downloaded according to the OSS Multi Product Quick Install Guide. They will be used in subsequent steps in this set up procedure. • Oracle Database 11g R2 (11.2.0.3) Enterprise Edition from My Oracle Support. Oracle Database can be found in Patches and Update. Perform a Patch Search for Patch Name or Number “10404530”. • Oracle JDeveloper 11g from Oracle Technology Network (OTN). JDeveloper and ADF can be found in the Downloads menu under Fusion Middleware. Choose the Oracle JDeveloper 11g Release 1 Windows install for Studio Edition (11.1.1.x). • Oracle WebLogic Server 10.3.6 (Fusion Middleware 11g R1 PS5) from http://edelivery.oracle.com/ as the Oracle Fusion Middlware product pack or from Oracle Technology Network (OTN) Downloads for Fusion Middleware. Follow the link for See All Fusion Middleware (11.1.1.x) downloads to find FMW 11.1.1.6. • Oracle Communications Order and Service Management 7.2.2 from http://edelivery.oracle.com/ under Oracle Communications Applications. • Oracle Communications Unified Inventory Management 7.2.2 from http://edelivery.oracle.com/ under Oracle Communications Applications. • Oracle Communications ASAP 7.2.0 from http://edelivery.oracle.com/ under Oracle Communications Applications. • Oracle Communications Design Studio 7.2.2 from http://edelivery.oracle.com/ under Oracle Communications Applications. This is used in combination with the Design Studio plug-ins for each application (OSM, UIM, ASAP), which are available from the application’s media pack. o Design Studio Platform - 7.2.2 o Design Studio for Domain Modeling - 7.2.2 o Design Studio for Order and Service Management - 7.2.2 o Design Studio for Order and Service Management Integration - 7.2.2 o Design Studio for Order and Service Management Orchestration - 7.2.2
  9. 9. OSS MOBILE SOLUTION UPTAKE GUIDE Page 8 o Design Studio for Order and Service Management Orchestration Application Integration Architecture (AIA) - 7.2.2 o Design Studio for Unified Inventory Management - 7.2.2 o Design Studio for Activation UI - 7.2.2 o Design Studio for Activation SRT - 7.2.2 The following additional packages of solution components must be downloaded. They will be used in subsequent steps in this set up procedure. • Oracle SQL Developer from Oracle Technology Network (OTN). SQL Developer can be found in the Downloads menu under Developer Tools. Choose the latest available release. • GSM technology pack for UIM from http://edelivery.oracle.com/ under Oracle Communications Applications. • Note: The UIM GSM technology pack contains the Mobile Data Dictionary cartridge (ora_dict_mobile), which is also used by the ASAP and OSM Mobile Solution cartridges. • Mobile Messaging cartridge media pack for ASAP from http://edelivery.oracle.com/ under Oracle Communications Applications (the media pack for Solaris is appropriate for all platforms). • Mobile Switching cartridge media pack for ASAP from http://edelivery.oracle.com/ under Oracle Communications Applications. • Mobile Service Provisioning Solution media pack from My Oracle Support (http://support.oracle.com). See Appendix A for details about the contents of the media pack. • Optionally, soapUI from http://www.soapui.org/ Server Platform Components The following hardware, operating system, and application server platform components are required by the solution. • Oracle Enterprise Linux on x86-64 hardware; or Oracle Solaris on SPARC hardware • Oracle Database 11g R2 (11.2.0.3) Enterprise Edition • Oracle WebLogic Server 10.3.6 (Fusion Middleware 11g R1 PS5) The installation procedures specific to each platform component should be followed. Follow the instructions in the OSS Multi Product Quick Install Guide. Separate schemas with separate table spaces (on a single database instance) should be created for each application. Single Domain Deployment A single WebLogic domain should be created to accommodate all applications (OSM, UIM, and ASAP). Each application will reside in its own managed server or cluster within the single domain. The managed server for each application should be named uniquely across domains. For example, OSM_MS1, UIM_MS1, ASAP_MS1. Uniqueness of server names is required for proper forwarding of JMS messages. Using a default name of AdminServer for each server will have catastrophic consequences. Multiple Domain Deployment A separate WebLogic domain should be created to accommodate each application (OSM, UIM, and ASAP). Each application will reside in its own distinct domain. The application server for each application should be named uniquely across domains. For example, OSM_MS1, UIM_MS1, ASAP_MS1. Uniqueness of server names is required for proper forwarding of JMS messages. Using a default name of AdminServer for each server will have catastrophic consequences. The domain name for each application should be named uniquely. For example, osmdomain, uimdomain, asapdomain. Using a default name of mydomain for each domain will have catastrophic consequences.
  10. 10. OSS MOBILE SOLUTION UPTAKE GUIDE Page 9 Server Applications The following server applications are required by the solution: • OSM 7.2.2 • UIM 7.2.2 • ASAP 7.2.0 Follow the instructions in the OSS Multi Product Quick Install Guide. The instructions will not be duplicated here. Solution Development Desktop The following desktop applications for Windows are also required by the solution. • Oracle SQL Developer • ADF Runtime for Windows • WebLogic Server 10.3.6 (FMW 11g R1 PS5) • Java JDK 1.6.0_37 • OSM Administrator (installed selecting the Custom Installation option on the OSM 7.2.2 windows installer) • OSM Software Development Kit (SDK) (installed selecting the Custom Installation option on the OSM 7.2.2 windows installer) • Design Studio for OSM, UIM, and ASAP. Note: remember to edit the preferences (under the Window / Preferences menu) to configure the OSM SDK under Oracle Design Studio / Order and Service Management Preferences. • soapUI (optional) The installation procedures specific to each application should be followed. The additional installation steps required for the solution are: 1. Install the following Design Studio plugins: • Oracle Communications Design Studio Platform • Oracle Communications Design Studio Domain Modeling • Oracle Communications Design Studio for Activation SRT • Oracle Communications Design Studio for Activation UI • Oracle Communications Design Studio for Inventory • Oracle Communications Design Studio Integration • Oracle Communications Design Studio for Order and Service Management • Oracle Communications Design Studio for Order and Service Management Orchestration • Oracle Communications Design Studio for Order and Service Management Orchestration Application Integration Architecture (AIA) 2. Configure the Design Studio preferences for OSM to recognize the paths to the Java Development Kit, WebLogic Server, and the OSM SDK. Using the Window / Preferences menu, the settings are under Oracle Design Studio / Order and Service Management Preferences. 3. Configure the Design Studio class path variable for WL_LIB to point to the WebLogic Server lib directory. 4. Obtain all the UIM jars relevant to solution development and copy them to a UIM lib directory. • capacity_caps.jar
  11. 11. OSS MOBILE SOLUTION UPTAKE GUIDE Page 10 • characteristic_caps.jar • consumable_caps.jar • core_caps.jar • groupenabled_caps.jar • ora_uim_commonLib.jar • persistence.jar • platform-persistence.jar • platform_managers.jar • uim-api-framework.jar • uim-caps.jar • uim-entities.jar • uim-entity-xmlbean.jar • uim-managers.jar • uim-tools.jar • uim-webservices-base.jar • uim-webservices-framework-xsd.jar • uim-webservices-framework.jar 5. Configure the Design Studio class path variable for UIM_LIB to point to the UIM lib directory. 6. Disable “Build Automatically”. A single installation of Design Studio will accommodate OSM, UIM, and ASAP working together in the same solution development workspace. It is not recommended to use separate installations of Design Studio for each of the applications, as this will not enable the user to take advantage of features that cross application boundaries for solution development. Extract the GSM Technology Pack for UIM using an unzip tool to expose the following components: 1. Mobile Data Dictionary cartridge: /designStudio/cartridgeZips/ora_dict_mobile_cartproj-7.2.2.0.0.*.zip 2. Service Profile Loader: /test/readinessDataLoader/serviceProfileLoader.sql 3. SIM-IMSI Loader: /test/readinessDataLoader/SIMIMSILoader.sql 4. Cartridge projects /designStudio/cartridgeZips/* Import the Mobile Data Dictionary cartridge project into the Design Studio workspace. Extract the following from their enclosing media packs using an unzip tool: • Ericsson HLR cartridge from the Mobile Switching media pack for ASAP • Comverse VVMS Insight cartridge from the Mobile Messaging media pack for ASAP Import the Ericsson HLR and Comverse VVMS cartridges for ASAP into the Design Studio workspace. These are not cartridge projects, so they will need to be imported as activation cartridges. Extract the Mobile Service Provisioning Solution media pack using an unzip tool to expose the following components: • Mobile Solution Installer (located in the ‘SolutionInstaller’ sub-directory of the media pack) • The Design Studio cartridge projects for the following solution components:
  12. 12. OSS MOBILE SOLUTION UPTAKE GUIDE Page 11 o Mobile Service for ASAP (composed of a single ASAP cartridge in AsapMobileCartridge.zip) o Mobile Service for OSM (composed of several OSM cartridges in OsmMobileCartridges.zip) Import the Mobile Service cartridge project for ASAP and OSM into the Design Studio workspace. Obtain the following base cartridge projects for UIM (from the UIM server deployment), and import them into the Design Studio workspace: • ora_uim_model • ora_uim_mds • ora_uim_baseextpts • ora_uim_basemeasurements • ora_uim_baserulesets • ora_uim_basespecifications • ora_uim_basephone_mgmt • ora_uim_uk_tn • ora_uim_us_tn • ora_uim_canada_tn • ora_uim_norway_tn • ora_uim_saudi_arabia_tn Import the remaining cartridge projects from the GSM technology pack for UIM into the Design Studio workspace. • ora_uim_address • ora_uim_canada_address • ora_uim_mobile_activation_profiles • ora_uim_mobile • ora_uim_mobile_service_profiles • ora_uim_mobile_service_registries • ora_uim_mobile_subscription • ora_uim_norway_address • ora_uim_party_customer • ora_uim_saudi_arabia_address • ora_uim_service_location • ora_uim_uk_address • ora_uim_us_address • ora_uim_voice_mail Messaging Resource Adapter To prepare the ASAP managed server for supporting a messaging bridge, the jms-notran-adp.rar resource adapter must be deployed. The resource adapter is located in WL_HOME/server/lib/jms-notran-adp.rar.
  13. 13. OSS MOBILE SOLUTION UPTAKE GUIDE Page 12 1. Install jms-notran-adp.rar as an application and target the ASAP managed server. a. From the WebLogic admin console, Lock & Edit. b. Go to the Deployments, and choose Install. c. Navigate to the WL_HOME /server/lib directory, choose the jms-notran-adp.rar resource adapter, and go to Next. d. Choose the “Install this deployment as an application” option, and go to Next. e. Target the ASAP managed server, and go to Next. f. Keep the “Use the defaults defined by the deployment's targets” setting. The name may be edited or left unchanged. Go to Finish. g. Activate Changes. 2. The jms-notran-adp deployment should be in a Prepared state. 3. Start the jms-notran-adp application. This enables the JNDI name eis.jms.WLSConnectionFactoryJNDInoTX on the ASAP managed server. Mobile Solution Installer First, configure the installer for the server environment. Using a text editor, edit the file mobile_setup.properties. Then, from the server where the WebLogic domain directories are accessible, the mobile solution installer will be run once to setup the application server resources in the server environment. Table 1 lists and describes the mobile_setup.properties attributes and values. Table 1 mobile_setup.properties Attributes and Parameters Property Description Example value solution_deployment _model SINGLE_DOMAIN=1 MULTIPLE_DOMAIN=2 1 osm_admin_url T3 URL to the admin server for administering OSM. In a single domain deployment model all applications will use the same admin server. t3://mclaren.us.oracle.com:9101 osm_domain_dir The full path to the WebLogic domain directory for OSM. /home/fmw/user_projects/domains/osmdo main osm_login The WebLogic administrator on the admin server for OSM. weblogic osm_password The WebLogic administrator password. weblogic$123 osm_cluster The name of the OSM cluster (empty if non-clustered). osm_cluster osm_servers The list of managed servers for OSM. osm_ms1,osm_ms2 osm_server_urls The T3 URL to the OSM managed server or cluster. t3://osm_ms1:8404,osm_ms2:8405 osm_app_url HTTP URL to the OSM application. http://osm_proxy:8403/OrderManagement asap_admin_url T3 URL to the admin server for administering ASAP. In a single domain deployment model all applications will use the same admin server. t3://mclaren.us.oracle.com:9101 asap_domain_dir The full path to the WebLogic domain directory for ASAP. /home/fmw/user_projects/domains/asapdo main asap_login The WebLogic administrator on the admin server for OSM. weblogic asap_password The WebLogic administrator password. weblogic$123 asap_server The managed server for ASAP. asap_ms asap_server_url T3 URL to the ASAP managed server. t3://asap_ms:8406 asap_env The ASAP environment id. Multiple ASAP deployments may be deployed in a single application server; each deployment is identified by a unique environment id. ENV1 uim_admin_url T3 URL to the admin server for administering UIM. In a single domain deployment model all applications will use the same admin server. t3://mclaren.us.oracle.com:9101 uim_domain_dir The full path to the WebLogic domain directory for UIM. /home/fmw/user_projects/domains/uimdo main uim_login The WebLogic administrator on the admin server for OSM. weblogic uim_password The WebLogic administrator password. weblogic$123 uim_cluster The name of the UIM cluster. uim_cluster uim_servers The list of managed servers for UIM. uim_ms1,uim _ms2
  14. 14. OSS MOBILE SOLUTION UPTAKE GUIDE Page 13 uim_server_urls The T3 URL to the UIM managed server or cluster. t3://uim _ms1:8408,uim _ms2:8409 uim_app_url HTTP URL to the UIM application. http://uim _proxy:8407/Inventory The following steps have been provided in the run.sh script for convenience: 1. If osm_cluster is not empty (meaning OSM is deployed as a cluster), the osm_server_urls must specify a T3 URL with a cluster address in the format t3://osm_ms1:8404,osm_ms2:8405 (where osm_ms1 and osm_ms2 are the managed server host addresses and 8404 and 8405 are the port numbers on the respective managed servers). 2. If uim_cluster is not empty (meaning UIM is deployed as a cluster), the uim_server_urls must specify a T3 URL with a cluster address in the format t3://uim_ms1:8408,uim_ms2:8409 (where uim_ms1 and uim_ms2 are the managed server host addresses and 8404 and 8405 are the port numbers on the respective managed servers). 3. After the mobile_setup.properties file has been edited, and the JAVA_HOME and WL_HOME environment variables are set, the mobile solution installer can be run from a server with access to the WebLogic domain directories. For a multi-domain deployment, all three domain directories must be accessible. It must have access to the domain directories to be able to encrypt passwords appropriate to the security realm for each domain. 4. Before the mobile solution installer can be run, ensure that an explicit File Store or JDBC Store has been configured for OSM. By default, the OSM installer configures its JMS servers to use the default persistent store, which is not a migratable service. This is not sufficient for a highly available deployment. An explicit persistent store for OSM is a pre-requisite. 5. Before the mobile solution installer can be run, all ASAP, OSM, and UIM managed servers must be shut down. This leaves only the Admin Server running for each domain, as well as any proxy servers (inconsequential). If any managed servers are running, while the mobile solution installer is executed, it will fail; to recover, shut down all managed servers and re-run the mobile solution installer. The following steps can be used to execute the mobile solution installer: JAVA_HOME=/home/oracle/Oracle/Middleware/jdk160_33 WL_HOME=/home/oracle/Oracle/Middleware/wlserver_10.3 JAVA_HOME/bin/java -cp WL_HOME/server/lib/weblogic.jar weblogic.WLST mobile_setup.py The mobile solution installer performs the following steps: 1. Configures OSM with JMS reply-to destinations for integrating with UIM. 2. Configures OSM with JMS reply-to destinations and an event topic for integrating with ASAP. 3. Configures OSM with a Store-and-Forward agent for sending requests to UIM. 4. Configures OSM with a Store-and-Forward agent for sending requests to ASAP. 5. Configures UIM with a Store-and-Forward agent for sending replies to OSM. 6. Configures ASAP with a Store-and-Forward agent for sending replies and events to OSM. 7. Configures ASAP with a Messaging Bridge for copying events to a SAF Queue that forwards to OSM. The Configuring OSM-UIM-ASAP JMS Messaging document is available from the Knowledge Base under My Oracle Support. This document details the application server resources that are configured by the mobile solution installer script. This detailed information will be useful to solution developers, who wish to extend the installer script to accommodate additional solution components that must be integrated. After the mobile solution installer has been executed, the managed servers for ASAP, OSM, and UIM can be restarted. The ASAP managed server can be started with the standard startManagedWebLogic script. If OSM is clustered, an OSM managed server must be started with an OSM-specific startup script that identifies the appropriate Coherence parameters file; otherwise, the standard startManagedWebLogic script can be used to start the OSM managed server. A UIM managed server must be started with a UIM-specific startup script that sets the appropriate environment variables.
  15. 15. OSS MOBILE SOLUTION UPTAKE GUIDE Page 14 Solution Components The following sections describe mobile GSM solution components. OSM Cartridges Perform the following steps in Design Studio to setup your workspace for OSM and ASAP solution development. 1. Open Eclipse using a new workspace. 2. Go to Help>Install New Software> and add a new update site. Provide the ftp or file URL to the update site containing the Design Studio plugins. 3. Install the following Design Studio plugins from that site: a. Activation SRT b. Activation UI c. Domain Modeling d. Inventory e. Order and Service Management f. Order and Service Management Integration g. Order and Service Management Orchestration h. Order and Service Management Orchestration Application i. Platform 4. Go to Window>Open Perspective>Other… and choose the Studio Design perspective. 5. Go to Window>Show View>Package Explorer 6. Turn off the Build Automatically setting under Project>Build Automatically. (This step is optional. It will prevent the entire workspace from being built when you don’t want it to. A build can always be scheduled by selecting Project>Clean and then choosing a project or the entire workspace.) 7. Go to Window>Preferences>Oracle Design Studio>Order and Service Management Preferences – set the WebLogic Home, Java SDK Home and OSM SDK Home 8. Go to Window>Preferences>Oracle Design Studio>Order and Service Management Preferences>Application Integration Architecture Preferences – set the Oracle Middleware Home 9. The Mobile Data Dictionary cartridge needs to be imported into the Design Studio workspace. 10. Go to the Cartridge View, right click and choose Import > Import Project. 11. In the popup window select the radio button for “Select archive file:” 12. Using the browse button find the “ora_dict_mobile_cartproj-1.0.0.0.0.*.zip” file that was extracted from the UIM GSM Technology pack and click ok. 13. Make sure the “Copy projects into workspace” checkbox is selected. The ASAP cartridges need to be imported into the Design Studio workspace. See the ASAP Cartridges section for details on where to get them. Each of the ASAP cartridges (sar files) is imported in the Studio Design perspective using the Import Activation Archive function by right clicking on the Cartridge View and choosing the Import Activation Archive menu item. 1. Under the Project menu, select Clean to start a build. Ensure the “Clean all projects” and the “Build the entire workspace” radio buttons are selected. The build should produce no errors in the Problems tab. 2. The OSM cartridges now need to be imported into the Design Studio workspace.
  16. 16. OSS MOBILE SOLUTION UPTAKE GUIDE Page 15 3. Go to the Cartridge View, right click and choose Import>ImportProject. 4. In the popup window select the radio button for “Select archive file:” 5. Using the browse button find the OsmMobileCartridges.zip file that was downloaded and click ok. 6. Make sure the “Copy projects into workspace” checkbox is selected. The following 28 cartridges should now be copied into your workspace: 1. ActivationOSMIntegrationDataDictionary 2. OracleComms_OSM_CommonDataDictionary 3. MobileGSMDelivery-composite 4. MobileGSMDelivery-ActivateFunction 5. MobileGSMDelivery-CancelFunction 6. MobileGSMDelivery-NumberPortFunction 7. MobileGSMDelivery-Orchestration 8. MobileGSMDelivery-ProductClasses 9. MobileGSMDelivery-ProductSpecification 10. MobileGSMDelivery-SupplyChainFunction 11. MobileGSMDelivery-Topology 12. MobileGSMDelivery-TruckRollFunction 13. MobileGSMDelivery-Utilities 14. MobileGSMProvisioning-ApproveFunction 15. MobileGSMProvisioning-CalculateDeliveryFunction 16. MobileGSMProvisioning-CompleteFunction 17. MobileGSMProvisioning-Composite 18. MobileGSMProvisioning-DesignFunction 19. MobileGSMProvisioning-GetConfigurationFunction 20. MobileGSMProvisioning-Orchestration 21. MobileGSMProvisioning-PostDesignFunction 22. MobileGSMProvisioning-PreDesignFunction 23. MobileGSMProvisioning-ProductClasses 24. MobileGSMProvisioning-ProductSpecifications 25. MobileGSMProvisioning-Topology 26. MobileGSMResources 27. ServiceProvisioning 28. Mobile_NumberPortabilityEmulator The ActivationOSMIntegrationDataDictionary project is required to be imported into the Design Studio workspace to properly build the other cartridges, but is NOT deployed to the OSM server run time.
  17. 17. OSS MOBILE SOLUTION UPTAKE GUIDE Page 16 The Mobile_NumberPortabilityEmulator project needs to be deployed for the Number Porting scenarios only. These scenarios include: Add with a PortIn TN and Disconnect with a PortOut TN. The emulator does not need to be deployed to run any of the other test cases. The emulator project is deployed using Ant. Follow these steps to correctly configure this in your workspace. 1. Go to Window>Show View>Other and select Ant. 2. Open the Ant tab and add the build file for the NPEmulators. Do this by clicking on the icon of an ant with a green plus sign beside it. In the Buildfile Selection popup, navigate to the Mobile_NumberPortabilityEmulator select the build.xml and click ok. 3. Highlight the NumberPortabilityEmulator in the Ant tab and right click>RunAs>Ant Build… 4. In the Configuration window, navigate to the Build tab. Uncheck the “Build before launch” checkbox. 5. Go to the JRE tab and make sure the Runtime JRE is set to “Separate JRE”. Click on the “installedJRE’s” button and edit the location of jre6. (it will likely be <middlewarehome>/jdk160_33/jre) 6. Save all changes. 7. In the Studio Design Perspective, go to the Package Explorer View. In the Mobile_NumberPortabilityEmulator rename the hostname.properties file so that it reflects your machine name. (This must be your Windows machine name. From a Command shell, execute “echo %COMPUTERNAME%”.) 8. Open the properties file and edit the variables to reflect your environment. Even though Design Studio is running on Windows, the paths should be specified with forward slashes ('/') as directory separators. • wls.user – the WebLogic Server admin user • wls.password – the WebLogic Server admin password • wls.url – the WebLogic admin server url • wls.target – the OSM managed server or cluster to target, when deploying the emulator. This should be same target where the OSM application is targeted. • osm.lib.dir=C:/Program Files/OSM/SDK/Automation/automationdeploy_bin – this is the path under the OSM SDK • wls.lib.dir=C:/fmw/wlserver_10.3/server/lib – this is the path to the WebLogic Server lib directory • jdev.lib.dir=C:/fmw/modules – this is the path to the JDeveloper modules directory • emulators.name=NumberPortabilityEmulator – this can be left unchanged The security principal for these emulators is configured for the user “admin”. If this is not a valid user in your domain, then you need to make the following edits: 1. Open the ejb-jar.xml file found in external_emulator_descriptor/META-INF and update <role-name> in 2 locations to reflect a valid user for your domain. 2. Open the weblogic-ejb-jar.xml (in the same directory) and update all values in both the <security-role-assignment> and <run-as-role-assignment> sections with the same user. 3. Go back to the Ant tab and expand the NumberPortabilityEmulator. From here you can double click on any of the targets. Double click on the “deploy_emulators” target to clean, build and deploy the emulators to the environment specified in your properties. The remaining 4 cartridges will need to be deployed, after making the appropriate edits and rebuilding. These configuration changes are required to reflect the server environment.
  18. 18. OSS MOBILE SOLUTION UPTAKE GUIDE Page 17 1. Using the Studio Design Perspective, go to the Cartridge View. In the MobileGSMDelivery-ActivateFunction cartridge, open the GSMDeliveryTask entity which is an Activation task. 2. Go to the Activation Task Details tab, and ensure that the JMS topic for events has enabled the “Use a queue” option. 3. Using the same perspective, open the MobileGSMDelivery-Composite cartridge editor. Go to the Model Variables tab and edit the value for ACTIVATION_ENV_ID to match the ASAP environment id. 4. Using the Studio Design Perspective go to the Package Explorer view. In the MobileGSMResources cartridge, edit the resources/GSMDataMapping.xml. In both the ‘resolutionURLPrefix ‘and ‘resolutionURL’ edit the ip and port number to reflect the UIM application so that the proper hyperlink will be displayed on the order fallout screen. 5. Under the Project menu, choose clean to start a build. You can either choose to build the entire workspace again, or only the OSM cartridges. The build should produce no error markers. Create a Studio Environment named “OSM_Env” (or any name you prefer) using the following steps: 1. Under the Studio menu choose New / Studio Environment and name it “OSM_Env”. 2. In the Cartridge Explorer, right click on the “OSM_Env” project and choose New / Environment / Studio Environment. Name it “OSM_Env”. 3. Set the Address to the URL for the OSM Cartridge Deployment Web Service which is typically deployed to a weblogic server or cluster. e.g., http://srvpldv5.us.oracle.com:8101/cartridge/wsapi where 8101 is the port for the weblogic server or proxy. 4. Scroll down to the Order and Service Management Test Submission URL section. 5. In the Web UI URL change ‘osmwebui’ to ‘OrderManagement/orchestration’ 6. Save. Deploy each of the OSM cartridges to the OSM_Env environment using the sceadmin login for OSM in the following sequence. You may ignore any warnings. 1. MobileGSMProvisioning-Composite 2. MobileGSMDelivery-Composite OSM Workgroup Membership This must be done after deploying the mobile service provisioning cartridges to the OSM server from Design Studio.The following procedure grants OMS_client access to the oms-automation user. 1. Login as the weblogic administrator to the OSM server’s WebLogic console. 2. Go to the security realm and look at the Users and Groups. 3. Open the oms-automation user and look at the Groups that the user is a member of. 4. Add the OMS_client group to the oms-automation user, if the user is not already a member. 5. Save. The procedures in this section require that the OSM admin user account must have 'Administrators' privilege. 1. Login as the weblogic administrator to the OSM server’s WebLogic console. 2. Go to the security realm and look at the Users and Groups. 3. Open the admin user (the login name is up your choice) and look at the Groups that the user is a member of. 4. Add the Administrators group to the admin user, if the user is not already a member.
  19. 19. OSS MOBILE SOLUTION UPTAKE GUIDE Page 18 5. Save The following procedure grants access to the mobile service provisioning cartridges to the admin user. 1. Run the OSM Administrator tool from Windows and login to the OSM server as admin. If this user is not authorized, then the admin user must be added as a member of the Administrators group in the WebLogic security realm (via the WebLogic console). 2. In the OSM Administrator tool, under the MobileGSMProvisioning-Composite cartridge, add the admin user to the GSMProvisioningRole workgroup. This authorizes the admin user to execute the tasks within this cartridge. 3. Add the osm-automation user to the GSMProvisioningRole workgroup. 4. In the OSM Administrator tool, under the MobileGSMDelivery-Composite cartridge, add the admin user to the GSMDeliveryRole workgroup. This authorizes the admin user to execute the tasks within this cartridge. 5. Add the osm-automation user to the GSMDeliveryRole workgroup. 6. When exiting the Administrator, be sure to update the server cache, which saves the changes to OSM. Additional users may be authorized in the same manner, after following the relevant procedure (not duplicated here) for creating OSM users in the authentication provider within the WebLogic security realm, and authorizing that user by granting membership in groups. WebLogic Credentials When requests are sent to external systems, credential information (username/password) is included in the security header of the message. It is an Oracle security violation to have these credentials hard coded in plain text in the plug-in xquery file that creates the security header. OSM provides a way of retrieving these credentials from WebLogic in a secure way so that the plug- in code does not need to store this sensitive information. However, WebLogic must be configured properly so that OSM can retrieve the appropriate credential information. The following steps must be performed to create the necessary credentials and credential stores required by the mobile solution. 1. In the MobileGSMResources cartridge navigate to the resources/credentials directory and save each of the xml files to the following directory <OSMInstallation>SDKXMLImportExportconfig 2. Open the osm-cred.xml file and edit the ‘user’ value. This should be a user that exists in the WebLogic security realm and belongs to the ‘OSM_ws_api’ group. Generally this is the default OSM Administrative user. (Leave all other values unmodified.) 3. Do the same for asap-cred.xml and uim-cred.xml. In general the names in these files are used by the installer so may not need to be edited. 4. In the <OSMInstallation>SDKXMLImportExportconfig directory, copy the sample config.xml file to a file that will be customized to the deployment environment. 5. Edit the copy of the config.xml file to ensure that at least the j2eeAdminConnection section is filled in with the appropriate environment details. Omit the password from this section. You will provide it on the command line. 6. Open a command prompt and navigate to the <OSMInstallation>SDKXMLImportExport directory. 7. Ensure that the JAVA_HOME and MIDDLEWARE_HOME environment variables exist on the desktop. Alternately this can also be set in the <OSMInstallation>SDKXMLImportExportconfig.bat file. 8. Run the EncryptPasswords.bat in order to encrypt the password in the j2eeAdminConnection of the config.xml file. EncryptPasswords .configconfig.xml -wlsUser 9. Run the credStoreAdmin.bat 3 times – once for each of the xml files you just copied: • credStoreAdmin ./config/osm-cred.xml ./config/config.xml -j2eeAdminPassword $WlAdminPassword $WlAdminUserName $WlAdminServerHost $WlAdminServerPort
  20. 20. OSS MOBILE SOLUTION UPTAKE GUIDE Page 19 • credStoreAdmin ./config/uim-cred.xml ./config/config.xml -j2eeAdminPassword $WlAdminPassword $WlAdminUserName $WlAdminServerHost $WlAdminServerPort • credStoreAdmin ./config/asap-cred.xml ./config/config.xml -j2eeAdminPassword $WlAdminPassword $WlAdminUserName $WlAdminServerHost $WlAdminServerPort Note: The weblogic server details are for the weblogic admin server in the domain where OSM is installed. 10. You will be prompted to input each user’s password when you run the batch file. ASAP Cartridges From http://edelivery.oracle.com/ under Oracle Communications Applications for Sun Solaris SPARC (32-bit) in the Oracle Communications ASAP Cartridges Media Pack, download the following ASAP cartridges: • Oracle Communications ASAP Mobile Switching Cartridges • Oracle Communications ASAP Mobile Messaging Cartridges Extract these archives to obtain the following cartridges of interest: • ERICSSONHLR_12_X_X_R1_1_0.b* • COMVERSEVIDEOMAIL_3_7_X_R1_0_0.b* Extract the AsapMobileCartridge.zip file from the Mobile Service Provisioning Solution media pack. Import the Ericsson and Comverse cartridge SAR files to the Design Studio workspace using “Import > Import Activation Archive”: • EricssonHLR_R12-0.sar • ComverseVVMS_3-7-X_R1_0_0.sar Import the Mobile GSM ASAP zip file to the Design Studio workspace using “Import > Import Project”. • AsapMobileCartridge.zip Create a Studio Environment named “ASAP_Env” (or any name you prefer). Set the connection information to the URL for the ASAP Cartridge Deployment Web Service. e.g., http://srvpldv5.us.oracle.com:8201/cartridge/wsapi Before proceeding to deploy the ASAP cartridges, the ASAP server (SARM) needs to be started using the following procedure, after logging into the ASAP server environment, if it is not already running. 1. cd ~/ASAP 2. . Environment_Profile 3. scripts/start_asap_sys -d Deploy each of the ASAP cartridges to the ASAP_Env environment using the sceadmin login for ASAP. Note: If ASAP is installed on a separate weblogic domain from OSM use the cmws_studio user • EricssonHLR_R12-0.sar • ComverseVVMS_3-7-X_R1_0_0.sar • ora_asap_mobile_gsm.sar Alternatively, the Cartridge Management Tools can be used to deploy cartridges to ASAP. This includes command line tools and a task that can be invoked from Ant. The ASAP server (SARM) needs to be restarted using the following procedure, after logging into the ASAP server environment:
  21. 21. OSS MOBILE SOLUTION UPTAKE GUIDE Page 20 1. cd ~/ASAP 2. . Environment_Profile 3. scripts/stop_asap_sys -d 4. scripts/start_asap_sys -d UIM Tech Pack Deployment UIM cartridge and technology pack deployment may be done through Design Studio, but because the GSM technology pack is an archive of cartridges (a super-cartridge) it cannot be deployed conveniently in a single step through Design Studio. The Cartridge Deployer tool that is bundled with UIM must be used instead; this tool may be used to deploy all UIM cartridges and technology packs. This tool can be found in the directory where the UIM server is installed (under ~UIM/CartridgeDeployerClients/CartridgeDeployer/). If the user insists on using Design Studio to deploy the cartridges individually, the ora_uim_model and ora_uim_mds cartridge projects for UIM should be imported into the Design Studio workspace, before importing any other UIM cartridge projects. The following productized UIM cartridges, which can be found in the directory where the UIM server is installed (under $DOMAIN/UIM/cartridges/base), need to be deployed in order: 1. ora_uim_baseextpts 2. ora_uim_basemeasurements 3. ora_uim_baserulesets 4. ora_uim_basespecifications 5. ora_uim_basephone_mgmt 6. ora_uim_canada_tn 7. ora_uim_norway_tn 8. ora_uim_saudi_arabia_tn 9. ora_uim_uk_tn 10. ora_uim_us_tn This should be followed by the installation of the GSM technology pack. The file name of the deployable super-cartridge is of the form mobileGSM_7.2.2.xxx.jar where xxx is the build number. This file will contain all the mobile cartridges. UIM Solution Development This section is necessary only for solution developers who wish to view, customize or extend the GSM tech pack. This procedure is not required to use the mobile solution as-is (unmodified). The ora_uim_model and ora_uim_mds cartridge projects for UIM should be imported into the Design Studio workspace, before importing any other UIM cartridge projects. The full set of base cartridge listed in the UIM Tech Pack section must be imported into the Design Studio workspace. The mobileGSM_7.2.2.xxx.zip archive should be extracted. A set of cartridge projects will be found under the /designStudio/cartridgeZips folder of the archive contents. Each of these cartridge projects should be imported into the Design Studio workspace. These cartridge projects can be edited, rebuilt, and deployed to UIM from Design Studio in the course of solution development. OPERATIONS AND READINESS This section describes the operations and readiness procedures that prepare the solution for provisioning services.
  22. 22. OSS MOBILE SOLUTION UPTAKE GUIDE Page 21 UIM Readiness The unmodified Mobile service provisioning solution supports US locations, addresses, and telephone numbers by default; after-market customization is required to modify the solution to support other locales. Locations Create the following service locations: • Using the country specification, create an instance named “USA”. • Using the usCity specification, create an instance named “Frisco”. • Using the usStateCode specification, create an instance named “TX”. Mobile Serving Area Figure 3 shows the structure for one Mobile Serving Area with one HLR, one SMSC, one voiceMailServer, and one usTelephoneNumberBlock serving one zip code. Typically, this serving area will have more than one usTelephoneNumberBlock serving more than one zip code. There may be more than one HLR, more than one SMSC, and more than one voiceMailServer, if the number of subscribers in this serving area is large. Figure 3 – Implementation Model for Operations and Readiness The structure in Figure 3 is intended to support the following queries: 1. Search for available telephone number to reserve based on the zip code of the customer’s service address. 2. Search for HLR to utilize based on the zip code of the customer’s service address. 3. Search for VMS to utilize based on the zip code of the customer’s service address. 4. Search for SMSC to utilize based on the zip code of the customer’s service address. The following readiness procedure must be performed using the UIM user interface:. 1. A Service Location (Geographic Location) must be created for each zip code. These will be common across different types of services (e.g., VoIP, Video, Internet, etc.). The name must match the zip code (e.g., 75034).
  23. 23. OSS MOBILE SOLUTION UPTAKE GUIDE Page 22 2. A Mobile Serving Area (Inventory Group) must be created for each point of presence. Use a naming convention of Mobile:Region (e.g., Mobile:Frisco) for these Mobile Serving Areas to distinguish these inventory groups from those supporting other types of service. Associate this serving area (under Places) with the zip code Service Location(s) that it serves (with no role). 3. A usTelephoneNumberBlock (Telephone Number) must be created for each block of numbers represented by a telephone number prefix. The id (e.g., 2143870) and name (e.g., 214-387-0) must match the telephone number prefix for the block. This must be a member of a Mobile Serving Area, which it serves. 4. A range of usTelephoneNumber (Telephone Number) instances that are Owned must be created for each telephone number within a usTelephoneNumberBlock. These numbers should NOT be added as a member of a Mobile Serving Area, as this will have a negative performance impact by creating a large number of inventory group references, which will affect all the searches needed to auto-design the services. The name must start with the same telephone number prefix as its usTelephoneNumberBlock (e.g., 214-387-0000 to 214-387-0999), the tnType must be Owned, and the tnCountryCode is North America. 5. A Home Location Register (HLR) must be created for each Ericsson HLR that is installed (e.g., hlr001). This must be a member of a Mobile Serving Area, which it serves. 6. A MobileSubscriptionProfile (Logical Device Account) associated with the HLR (above) must be created for the Postpaid classOfSubscriber; and another one must be created for the Prepaid classOfSubscriber. The profileNumber should be set to a number that is unique to each profile. 7. A Short Messaging Service Center (SMSC) must be created for each Ericsson SMSC that is installed (e.g., smsc001). This must be a member of a Mobile Serving Area, which it serves. Note that in ASAP, there is no corresponding SMSC activation cartridge, because this device is only needed in inventory to provide the necessary information for activating SMS on the HLR; activation of the SMS service is not managed by communicating directly with the SMSC. 8. A voiceMailServer must be created for each Comverse VVMS Insight that is installed (e.g., vms001). This must be a member of a Mobile Serving Area, which it serves. 9. The device names of the HLR and voiceMailServer correspond to the element names in ASAP. This correspondence will be established in ASAP through the procedure described in the ASAP Readiness section. ASAP disallows the ‘:’ (colon) character from being used in this name; it must follow the conventions and constraints for a WebLogic MBean name.
  24. 24. OSS MOBILE SOLUTION UPTAKE GUIDE Page 23 Figure 4– Mobile Serving Area Service Profiles Perform the following procedure in Oracle SQL Developer: 1. Create a database connection to the UIM schema in the Oracle Database instance. 2. Open a SQL Worksheet to this database. 3. Open the serviceProfileLoader.sql script and execute it against the UIM schema. SIM Cards and IMSIs The following procedure is done from within Oracle SQL Developer: 1. Create a database connection to the UIM schema in the Oracle Database instance. 2. Open a SQL Worksheet to this database. 3. Open the SIMIMSILoader.sql script and make the following edits. a. loc_iccid_prefix varchar2(20) := '89014102211'; This constant is used as a prefix for the ICCID that identifies a SIM card. b. loc_iccid_postfix PLS_INTEGER := 6; This constant is used as a suffix for the ICCID to populate the check digit. This approach does not conform to the Luhn algorithm, as prescribed by the standard. c. loc_imsi_mcc PLS_INTEGER := 310; This constant is used as the mobile country code for the IMSI. d. loc_imsi_mnc PLS_INTEGER := 150; This constant is used as the mobile network code for the IMSI.
  25. 25. OSS MOBILE SOLUTION UPTAKE GUIDE Page 24 e. TOTAL_SIM_IMSI PLS_INTEGER := 10; This constant is the total number of SIM Cards and IMSI pairings that will be loaded into the inventory. f. loc_iccid_start PLS_INTEGER:= 1000010; This is the starting subscriber part for the range of ICCID numbers that will be generated. g. loc_imsi_msin_start PLS_INTEGER := 100000010; This is the starting MSIN part for the range of IMSI numbers that will be generated. The TOTAL_SIM_IMSI and the starting numbers for the ICCID and IMSI MSIN can be adjusted to generate a different range of SIM Cards and IMSI pairings for each run of this script. The ICCIDs are significant in that these identifiers will be expected to be input during Order Capture. The ICCID is usually scanned from a bar code that is printed on the package for the SIM Card. The pairing of the ICCID with an IMSI reflects the pre-activation of the IMSI (as a skeletal mobile service) on the HLR and AuC devices. 4. Execute the script against the UIM schema. ASAP Readiness Each HLR and VMS installed in the inventory must have a matching network element configured in ASAP. The network elements can be configured using Design Studio’s “NEP Map” functionality or by using ASAP’s SACT command-line utility. Both approaches will be described below. Before using either approach, login to the ASAP server and execute the script that sets the ASAP environment variables. cd ~/ASAP . Environment_Profile Ensure that the ASAP server is running, before proceeding. If it is not running, use the following command to start it. scripts/start_asap_sys -d Leave the terminal open and use it for any steps in the following sections that require command-line access. Configuring Network Elements using Design Studio’s NEP Map Before using the NEP Map functionality, it is first necessary to create Network Element entities in Design Studio for each HLR and VMS device. Start by creating a new Activation project for the Network Elements: 1. On the Cartridge View, right click and select “New > Project > Activation Project”. 2. Enter a project a name (e.g. “ASAP_NetworkElements”). 3. Select “Activation Service Cartridge” in the Cartridge Type field. 4. Click Next. 5. Enter values in the Service and Domain fields (e.g. “Mobile” and “GSM”). 6. Click Finish. 7. Open the Cartridge within the new project. 8. Go to the Dependency tab. 9. Click Add. 10. Select the Ericsson HLR and Comverse VVMS cartridges. 11. Click OK. 12. Save the Cartridge. To create an Ericsson HLR element: 1. On the Cartridge View, right click on the project that was created above and select “New > Network Element”
  26. 26. OSS MOBILE SOLUTION UPTAKE GUIDE Page 25 2. Select “NE_ERIC-HLR_R12-0-HOST” in the NE Template field 3. Uncheck “Use recommended name and location” 4. Change the Name field to match the logical device name from UIM NOTE: Design Studio will automatically convert all characters entered in this field to uppercase. Don’t be concerned if the HLR name in UIM contains lowercase characters. Instead, enter them as uppercase for now and they can be changed later in Step 8. 5. Click Finish 6. Open the newly created Network Element 7. Go to the Connections tab and check whether the values in the “ASAP System Setting” column match the installation mode that was selected during the ASAP installation (i.e. “Development” or “Production”). They will be listed as “Development” by default, so if ASAP was installed in Production mode, you will need to change the value to “Production” in each row. 8. Go to the Target Network Elements tab and confirm that the Target NE Name matches the value from UIM. If the name requires lowercase characters, then they can be entered at this point. If a change to the Target NE Name field is required, it is usually a good idea to rename the Network Element entity as well in order to maintain consistency. This can be accomplished by right-clicking on the entry in the Cartridge View and selecting Rename. NOTE: There is a restriction in Design Studio that won’t allow the Network Element name to be converted to lowercase directly. It will result in the following error: “Entity exists with a different case”. If you get this error, you can rename to an intermediate name first, and then to the desired name. For example, if the original name is “HLR001”, you will get an error trying to rename directly to “hlr001”. In this case, rename it to an intermediate name like “hlr001.x” first, and then to the final name of “hlr001”. 9. Make sure that any changes made for steps 7 and 8 have been saved. Repeat the steps listed above for any additional HLR’s and each VMS, but select “CMVT-VVMS_3-7-X-HOST” as the NE Template in Step 2. Once all of the Network Elements have been created, build the project as follows: 1. On the Cartridge View, double click on the entry for the newly created Activation project (e.g. “ASAP_NetworkElements”) 2. Select “Project > Build Project” from the main menu Deploy the Network Elements to ASAP using an NEP Map as follows: 1. Open the Studio Environment that was used earlier to deploy the cartridges to ASAP (e.g. “ASAP_Env”) 2. Open the “Activation Connection Details” sub-panel in the Studio Environment editor and update the Environment ID, Activation Version, Server Address, and Server Port Number fields appropriately. NOTE: The server address and port values will be the same WebLogic values that were already entered in the Address field at the top of the editor. 3. Save the changes 4. On the Cartridge View, right click on the Studio Environment entity and select “New > NEP Map” 5. Select the ASAP Studio Environment from the Studio Environment drop-down list
  27. 27. OSS MOBILE SOLUTION UPTAKE GUIDE Page 26 6. Enter a name in the Entity field (e.g. “NEP_MAP”) 7. Click Finish 8. Open the newly created NEP Map 9. Click the Add button and select the HLR that was created earlier 10. Repeat the previous step for all additional HLR’s and VMS’s 11. Click Connect and enter the WebLogic admin credentials 12. Once the NEP Map is connected, select the target ASAP NEP server from the Default NEP drop-down list (e.g. “NEP_<ENV_ID>”) 13. Click on each row in the table so that the NEP column gets filled in with the value that was selected in the previous step 14. Click Deploy All and monitor the status in the popup window to verify that it completes successfully The last step is to restart ASAP as described in the Restart ASAP section. Configuring Network Elements using SACT To add an Ericsson HLR as a network element using SACT: 1. Un-jar the Ericsson HLR cartridge (EricssonHLR_R12-0.sar) into an empty directory. 2. Edit a copy of the file NetworkElements/NE_ERIC-HLR_R12-0-HOST.xml 3. Copy or edit the <element name=” NE_ERIC-HLR_R12-0-HOST”> (through to the end tag for this element), and change the name to the logical device name from UIM (e.g., hlr001). Also rename the routingElement underneath it. 4. Any //connectionPool/device/environment elements containing the text “DEVELOPMENT” should be replaced by “PRODUCTION” to match the ASAP_SYS environment variable (whose value is set to “PROD”), if running in production mode. Otherwise, the environment element can be set to “DEVELOPMENT” to match the ASAP_SYS environment variable whose value is “TEST”. 5. In the ASAP environment, run: sactConfig NE_ERIC-HLR_R12-0-HOST.xml 6. Verify that sactConfig completed successfully (e.g. search for a “BUILD SUCCESSFUL” message in the command output) To add a Comverse Insight VVMS (voiceMailServer) as a network element using SACT: 1. Un-jar the Comverse Insight VVMS cartridge (ComverseVVMS_3-7-X_R1_0_0.sar) into an empty directory. 2. Edit a copy of the file NetworkElements/CMVT-VVMS_3-7-X-HOST.xml 3. Copy or edit the <element name=”CMVT-VVMS_3-7-X-HOST”> (through to the end tag for this element), and change the name to the logical device name from UIM (e.g., vms001). Also rename the routingElement underneath it. 4. Any //connectionPool/device/environment elements containing the text “DEVELOPMENT” should be replaced by “PRODUCTION” to match the ASAP_SYS environment variable (whose value is set to “PROD”), if running in production mode. Otherwise, the environment element can be set to “DEVELOPMENT” to match the ASAP_SYS environment variable whose value is “TEST”. 5. In the ASAP environment, run: sactConfig CMVT-VVMS_3-7-X-HOST.xml 6. Verify that sactConfig completed successfully (e.g. search for a “BUILD SUCCESSFUL” message in the command output) Restart ASAP as described in the following section.
  28. 28. OSS MOBILE SOLUTION UPTAKE GUIDE Page 27 Restart ASAP The ASAP server (SARM) needs to be restarted in order for the new Network Elements to become active within ASAP. The following commands should be run to restart ASAP: 1. cd ~/ASAP 2. scripts/stop_asap_sys -d 3. scripts/start_asap_sys -d The following command can be run to verify that the Network Elements have been successfully recognized by ASAP: 1. asap_utils –d 7 The new Network Elements should appear in the ‘Host_CLLI’ column. For example: NEP Host_CLLI Tech Sftwr State ... Retry_Count --------- ------------------ ---------- ---------- ---------- ... ----------- NEP_ENV1 HLR001 ERIC-HLR R12-0 Down ... 0 NEP_ENV1 VMS001 CMVT-VVMS 3-7-X Down ... 0 SAMPLE EBM ORDERS FOR MOBILE The MobileGSMProvisioning-Orchestration cartridge has a sample folder which contains enough orders to get most people started using the solution. The order prefix matches the test case name in RTH. It is also possible to create your own sample orders. There are two distinct steps required to get an order ready for submission to the Mobile GSM solution – each of which is detailed below. Tooling will be developed before GA to aid in the development and editing of Mobile orders. Before these tools are ready, the samples included in the solution should be used as a guide. Order Template creation The EBM orders are very large, complex structures that can contain a varying number of Provisioning Order Lines. Most of these POL’s, correspond to a mobile service attribute of some description. It is these line items that must be added or removed to the order depending on the use-case that this template is trying to support. The sample orders that come in the /samples directory of the MobileGSMProvisioning-Orchestration cartridge are order templates. For example, UTC98427_Order.xml is a template for adding a mobile service without Caller Id, Call Waiting, Call Forwarding, SMS, Voicemail or GPRS. The optional service attributes that have a corresponding provisioning order line are: • Caller ID • Call Waiting • Call Forwarding • SMS • Voicemail • GPRS There are other service attributes that aren’t represented as an order line item, but rather correspond to a piece of data somewhere on the line items that already exist in the template. These values should be set as part of the template creation as well and are detailed as follows: • Service action • TNType • Reserved For (if applicable) • Reserved Type (if applicable)
  29. 29. OSS MOBILE SOLUTION UPTAKE GUIDE Page 28 • Responsible Provider • Class of Subscriber Finally, the service address needs to be completed to match a geographic area that has been created in UIM. Template Creation – A walkthrough The first step is to outline the optional attributes that a template will support, and then create the template with the POL’s that are appropriate. 1. Make a copy of the Mobile_BaseTemplate.xml and give it a name to reflect the template you are building. (This file contains the necessary order header and POL sections that are required for a Mobile EBMPO. It can be found in MobileGSMProvisioning-Orchestration/samples. 2. Open the Mobile_MasterOrderTemplate.xml (It can be found in MobileGSMProvisioning-Orchestration/samples) 3. You are now going to copy Provisioning Order Lines that from the master into your template. You will identify the order lines by their “FIC” value and you will add them below the existing POL’s in your base template. FIC values can be found at this location in the master template. <corecom:ItemReference><corecom:ClassificationCode listID=”FulfillmentItemCode”> XXXX Table 2 Service Attributes and FIC Values Service Attribute FIC Value Caller Id Caller ID Feature Class Call Waiting Call Waiting Feature Class Call Forwarding Call Forwarding Feature Class Voicemail Voicemail Feature Class GPRS Data Service Feature Class SMS Text Messaging Class If you want to include SMS, you will need to copy a second POL that matches the following criteria: <corecom:ItemReference><corecom:ClassificationCode listID=”BillingProductTypeCode”>SERVICE BUNDLE <corecom:ItemReference><corecom:ClassificationCode listID=”PermittedTypeCode”> /service/gsm/sms The second step is to update the individual elements with values to match your use case. 1. Find the POL that matches the following criteria: <corecom:ItemReference><corecom:ClassificationCode listID=”BillingProductTypeCode”>SERVICE BUNDLE <corecom:ItemReference><corecom:ClassificationCode listID=”PermittedTypeCode”> /service/gsm 2. Update the service action code ( <provord:ProvisioningOrderLine><provord:ServiceActionCode>) with one of these options: ADD, SUSPEND, UPDATE, DELTE, RESUME 3. Update the service address (<provord:ProvisioningOrderLine><corecom:ServiceAddress>) with values to match UIM 4. Find the POL that matches the following criteria: <corecom:ItemReference><corecom:ClassificationCode listID=”FulfillmentItemCode”>Mobile GSM Service Plan Class 5. Update the Class Of Subscriber (<corecom:SpecificationGroup><corecom:Name>ExtensibleAttributes) with “Prepaid” or “Postpaid” 6. Update the Telephone Number Porting Type (<corecom:SpecificationGroup><corecom:Name>ExtensibleAttributes) with “Portin”, “Portout”, or “Reserved” 7. If this is a reserved use case, update the “Reserved For” and “Reserved Type” in the same extensible attribute area. 8. If this is a portin scenario, update the “ResponsibleProvider” attribute in the same extensible attribute area.
  30. 30. OSS MOBILE SOLUTION UPTAKE GUIDE Page 29 Order Template editing Once a template has been created, it needs to be updated with a few pieces of data that must change with each run of the order. These values are: • Service Correlation Id • TN (only on ADD action) • IccId (only on ADD action) Template editing – A walkthrough The following sections describe a template editing walkthrough. ADD Do the following procedure: 1. Find the POL that matches the following criteria <corecom:ItemReference><corecom:ClassificationCode listID=”BillingProductTypeCode”>SERVICE BUNDLE <corecom:ItemReference><corecom:ClassificationCode listID=”PermittedTypeCode”> /service/gsm 2. Edit the Telephone Number (<provord:ProvisioningOrderItemInstance><corecom:Identification><corecom:ID>) 3. Edit the Service Correlation Id (<corecom:InstalledProductReference><corecom:InstalledProductIdentification><corecom:Busi nessComponentID) 4. Find the POL that matches the following criteria <corecom:ItemReference><corecom:ClassificationCode listID=”FulfillmentItemCode”>SIM Product Class 5. Edit the ICCID (<corecom:SpecificationGroup><corecom:Name>ExtensibleAttributes) with a valid value from UIM. Follow on Actions (Suspend, Resume, Change, Disconnect) Do the following: 1. Find the POL that matches the following criteria. <corecom:ItemReference><corecom:ClassificationCode listID=”BillingProductTypeCode”>SERVICE BUNDLE <corecom:ItemReference><corecom:ClassificationCode listID=”PermittedTypeCode”> /service/gsm 2. Edit the ServiceCorrelationID <corecom:InstalledProductReference><corecom:InstalledProductIdentification><corecom:Busin essComponentID) DEMONSTRATION This section describes the procedures for demonstrating the provisioning solution. The Set Up and Operations and Readiness procedures must have been completed beforehand. There is a limited set of sample orders which can be found in the /samples directory of the MobileGSMProvisioning-Orchestration cartridge.
  31. 31. OSS MOBILE SOLUTION UPTAKE GUIDE Page 30 Add Mobile The following section describes the steps to add a mobile. Add Mobile with a Reserved Telephone Number Using OSM web UI Test Cases where a reserved telephone number are used must be handled differently than the others. Reservation information would not be captured by Siebel and would therefore not be part of the AIA order being submitted to OSM. The folloiwng procedure is for creating a service order that uses a reserved telephone number. 1. Create a new MobileGSMProvisioning order and note its order id for later. 2. Select the “add” service action. 3. Add a unique ID for the ServiceCorrelationID. This ID will be used to identify the correct service on follow on actions such as suspend, resume. 4. Enter a value for Line ID. 5. In the ProductClass field enter the value “MobileService” 6. Populate the Subscriber Name field. 7. Populate the serviceAddress with an addressLine1, city, state, countryCode and zipcode. For example, 1234 Main St, Big City, NY, USA 12001. Ensure that the zipcode is a valid serving area in UIM. 8. Enter a unique Correlation ID for the Business Interaction. This should be unique from one order to the next. 9. Click on the + sign to add an Attribute for each of the following name/value pairs. Table 3 Name Pair Values Name Value callerId Yes or No callForwarding Yes or No callWaiting Yes or No Sms Yes or No GPRS Yes or No Voicemail Yes or No classOfSubscriber prepaid or postpaid TNType RESERVED TN Leave empty for now ReservedFor The OSM order id ReservedForType Order iccId Leave empty for now 10. Save the order It would be perfectly acceptable to use the same id for the OSM order reference, the ServiceCorrelationID, the Reserved For, and the Correlation ID for the Business Interaction. In UIM: 1. Create a Reservation for a Telephone Number. 2. Reserved For Type: Order 3. Reserved For: input the order id from above 4. Reservation Type: Long-term 5. Search for an available telephone number and add one to the reservation. Note the TN for later. 6. Save 7. Search for an available SIM Card. 8. Note its ICCID for later.
  32. 32. OSS MOBILE SOLUTION UPTAKE GUIDE Page 31 In OSM, continue editing the same order: 1. Update the following attributes with the appropriate value 2. TN with the reserved Telephone Number from UIM. 3. Populate the ICCID with the ICCID of the SIM Card from UIM. 4. Submit the order for execution. Add Mobile with a Reserved Telephone Number In the case that the AIA provisioning order can be updated to pass in the Reservation information, then you can use the following procedure to submit a provisioning order. In OSM: 1. In Design Studio, from the samples directory open either UTC98427_Order.xml (no call features, sms, voicemail or GPRS) or UTC98428_Order.xml (with call features, sms, voicemail and GPRS) 2. Follow these steps to update a new TN, Service Correlation ID and IccId - Template editing – A walkthrough. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment you wish to send the order to. 5. Go to the OSM WebClient to watch the order progression Add Mobile with a Port-in Telephone Number This following procedure is for submitting a provisioning order for adding mobile service. In OSM: 1. In Design Studio, from the samples directory open either UTC98429_Order.xml (no call features, sms, voicemail or GPRS) or UTC98430_Order.xml (with call features, sms, voicemail and GPRS) 2. Follow these steps to update a new TN, Service Correlation ID and IccId - Template editing – A walkthrough. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment you wish to send the order to. 5. Go to the OSM WebClient to watch the order progression Cancel Scenario The following procedure is for cancelling an order that has reached the “HandleFallout” task. 1. From the worklist, select the applicable order 2. Right click and choose cancel 3. On the cancellation screen, choose “cancel immediately” 4. Confirm the cancellation 5. When the order rolls back to the creation task, select the order. 6. Choose the “delete” status The order will now be deleted from the worklist. All rollback work has been done at this point and the deletion is simply to clean up the worklist. Note: OSM does not allow a task to be defined with no statuses. As a result, the “HandleFallout” task has a status of “Finish”. This status SHOULD NOT be used. The only option the user should have from this fallout task is to cancel the order. Also note that this procedure is for the “HandleFallout” task and not the “HandleDesignFallout” task.
  33. 33. OSS MOBILE SOLUTION UPTAKE GUIDE Page 32 Retry Scenario The following procedure is for retrying an order that has reached the “HandleDesignFallout” task. 1. Accept the “HandleDesignFallout” task from the worklist. 2. Read the error details. 3. Make any necessary changes in UIM. 4. Select the retry status. Resume Scenario The following procedure is for resuming an order that has reached the “HandleDesignFallout” task. 1. Read the error details. 2. Edit the order data to contain valid values. 3. Select the resume status. Suspend Mobile This following procedure is for submitting a provisioning order for suspending a mobile service. 1. In Design Studio, from the samples directory open UTC98436_Order.xml 2. Follow these steps to update the Service Correlation ID with a value that corresponds to a previously created service. See the Follow on Actions (Suspend, Resume, Change, Disconnect) section. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment you wish to send the order to. 5. Go to the OSM WebClient to watch the order progression Resume Mobile This following procedure is for submitting a provisioning order for resuming a suspended mobile service. 1. In Design Studio, from the samples directory open UTC98437_Order.xml 2. Follow these steps to update the Service Correlation ID with a value that corresponds to a previously suspended service. See the Follow on Actions (Suspend, Resume, Change, Disconnect) section. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment you wish to send the order to. 5. Go to the OSM WebClient to watch the order progression Change Mobile The following section describes changing a mobile service. Change Mobile to add GPRS This following procedure is for submitting a provisioning order for adding GPRS to a mobile service. 1. In Design Studio, from the samples directory open UTC98440_Order.xml 2. Follow these steps to update the Service Correlation ID with a value that corresponds to a previously added service that did not have GPRS – See the Follow on Actions (Suspend, Resume, Change, Disconnect) section. a. With the order selected in the Package Explorer view, right click and choose Submit Test. b. Select the OSM environment you wish to send the order to. c. Go to the OSM WebClient to watch the order progression
  34. 34. OSS MOBILE SOLUTION UPTAKE GUIDE Page 33 There is an option to include additional validation at design time, to raise an error message when the user attempts to add a data service to a mobile service when it already exists. In order to add this option, the user should first create a copy of the service order specification in a design studio inventory workspace. The user should then associate the createBIAttachmentMobileServiceConfigBeforeExtPt extension point ruleset to the service order specification so that this validation is triggered when a service order is created in UIM. Change Mobile to remove GPRS This following procedure is for submitting a provisioning order for removing GPRS from a mobile service. 1. In Design Studio, from the samples directory open UTC98441_Order.xml 2. Follow these steps to update the Service Correlation ID with a value that corresponds to a previously added service that has GPRS – See the Follow on Actions (Suspend, Resume, Change, Disconnect) section. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment you wish to send the order to. 5. Go to the OSM WebClient to watch the order progression Additional validation options at design time are available to raise an error message when the user attempts to remove a data service from a mobile service when it has already been removed. In order to add this option, the user should first create a copy of the service order specification in a design studio inventory workspace. The user should then associate the createBIAttachmentMobileServiceConfigBeforeExtPt extension point ruleset to the service order specification so that this validation is triggered when a service order is created in UIM. Disconnect Mobile The following sections describe the steps to disconnect a mobile service. Disconnect This following procedure is for submitting a provisioning order to disconnect a mobile service. 1. In Design Studio, from the samples directory open UTC98439_Order.xml 2. Follow these steps to update the Service Correlation ID with a value that corresponds to a previously added service – See the Follow on Actions (Suspend, Resume, Change, Disconnect) section. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment. 5. Go to the OSM WebClient to watch the order progression Disconnect Mobile with a Port-Out Telephone Number This following procedure is for submitting a provisioning order to disconnect a mobile service and port out the TN. 1. In Design Studio, from the samples directory open UTC98438_Order.xml 2. Follow these steps to update the Service Correlation ID with a value that corresponds to a previously added service – See the Follow on Actions (Suspend, Resume, Change, Disconnect) section. 3. With the order selected in the Package Explorer view, right click and choose Submit Test. 4. Select the OSM environment. 5. Go to the OSM WebClient to watch the order progression TROUBLESHOOTING Please, refer to Troubleshooting Order Execution in the OSS Solution Development Best Practices and Guidelines document for a description of the procedure for how to troubleshoot problems in order execution.
  35. 35. OSS MOBILE SOLUTION UPTAKE GUIDE Page 34 Frequently Encountered Problems The following sections describe frequently encountered problems. Not enough logging from OSM to diagnose failures. Cause: the logging level is set to high severity, such as error, so warnings and informational messages are filtered out. Resolution: to enable more detailed messages to be logged during OSM solution development, the Log4JAdmin can be used to turn on logging of debug messages for specific classes. The Log4JAdmin console can be found at the following URL: http://<host>:<port>/oms/control/log4jAdmin JMS Store-and-Forward forwarded a message from OSM, but the message never arrives at the remote system. Cause: This problem is possibly caused by the JMS module name being identical in both domains. Resolution: Delete the JMS module in OSM and create it with a name different from the remote system. There is no way to rename the JMS module after it is created, so it must be deleted first. OSM continually retries executing the automation plug-in due to message re-delivery. Cause: This problem is possibly caused by a message that is being received by an automation receiver, but the message cannot be processed. The message is redelivered forever with the same outcome. Resolution: Delete the message from the Queue, and fix the problem in the automation script. Alternatively, during development it is often helpful to configure the Queue with Delivery Failure behavior such that the message is discarded after 2 re-delivery attempts. UIM cartridge deployment fails to find Extension Point. Cause: This problem is possibly caused by the need to refresh materialized views that have been created during performance tuning. Variations: Similar problems may arise due to materialized views on the InventoryConfigurationSpec table. After deploying a service cartridge such as voice mail, the configuration specification may not appear for some time. Resolution: Refresh the materialized views manually or wait for the refresh interval to pass. execute DBMS_SNAPSHOT.REFRESH_ALL; ASAP fails to send events. Cause: This problem is possibly caused by an incorrect weblogic password on the bridge destinations or on the SAF context for forwarding events remotely to the OSM server. The following error will be seen in the ASAP server log: weblogic.jms.common.IllegalStateException: Failed to send message to the destination 1.XVTEventTopic: The destination has been deleted Resolution: Use the WebLogic console to edit the passwords on the messaging bridge and the SAF context. APPENDIX A: CONTENTS OF THE MOBILE SERVICE PROVISIONING SOLUTION MEDIA PACK The Mobile Service Provisioning Solution Media Pack is distributed as a ZIP file named “MobileServiceProvisioning.zip”. It contains the following components: Table 4 Mobile Solution Components Component ZIP Artifact Name(s) Mobile Solution Uptake document (this document) OSS Mobile Solution Uptake.pdf Mobile Solution Installer SolutionInstaller/mobile_setup.properties SolutionInstaller/mobile_setup.py SolutionInstaller/run.sh Mobile Service cartridge for ASAP AsapMobileCartridge.zip Mobile Service cartridges for OSM OsmMobileCartridges.zip Mobile Solution README README.txt
  36. 36. OSS MOBILE SOLUTION UPTAKE GUIDE Page 35 NOTE: The Mobile Data Dictionary Cartridge (ora_dict_mobile) is not included in this Media Pack. It is only included in the UIM GSM Technology Pack.

×